In this post I describe a Rosyln analyzer you can use to enforce that primary constructors are only used for initialization and never to capture as fields
It’s nice to know I live rent-free in the minds of #dotnet folks, so much so that they felt the need to come by the BUILD booth to tell our JetBrains folks about me. 😅
This time I decided to go with the analysis based on the work initially made by @joaofbantunes. Be ready to see some assembly code generated by the JIT compiler, see some #dotnet source code and finally find if strong typing means poor performance or not.
C’è qualche novità per il web, nell’ambiente dei giochi C# e .NET. Già la roba fatta con quelle tecnologie poteva girare da anni sul web eh, ma… non farò finta di sapere cose che non so (non uso nessuna delle due tecnologie), ma ciò che voglio dire è che i gaymers sono passati all’attacco; ora pare esserci qualche risorsa in più, tipo FNA.WASM.Sample, che fa vedere come portare a WASM un gioco fatto con FNA-XNA. 🤔️
Quindi? Beh, un’idea venuta a caso la settimana scorsa era “cosa se portassi Celeste al browser?“, ma non ho poi fatto nulla, presa da altre cose. Volevo quasi quasi iniziare stamane, ma giusto per scrupolo cerco di nuovo sul web “celeste wasm”, sia mai che la volta scorsa mi era sfuggito qualcosa. E, nell’arco di precisamente questa settimana, non so se mi hanno letto nel pensiero o spiato spacctorium, ma hanno effettivamente iniziato e finito il fottutissimo celeste-wasm. Un po’ mi rode, ma meglio così, ho più tempo per altre imprese. 🤯️
Già a dir poco godurioso, ma qualcosa da sistemare rimane, tant’è che mi sono permessadi aprire la issue #1 per consigliare compressione e streaming degli asset. Vi invito a provare direttamente su https://celeste.r58playz.dev, ma per copyright hanno fatto che gli asset sono criptati e bisogna dare un file da un’installazione di Celeste per decifrarli… se vi serve, non lo linko, ma l’ho caricato sull’homeserver come altre volte, e se ravanate lo trovate. 👾️https://octospacc.altervista.org/2024/05/25/gayming-web/
Anybody know when we get the #Roslyn 4.10 NuGet packages (like Microsoft.CodeAnalysis)?
I'm assuming they're going to follow the "even" pattern and declare 17.10 as LTSC, which means I will want to officially support Roslyn 4.10. Both of these pages are currently out of date:
Is there any way to create/maintain a unique user id value for #blazor that goes across server-static and server-interactive pages? Other than a cookie, because that's too broad - I want something that is more per-tab than per-browser.
I'm sold on building my .NET NativeAOT Vulkan prototype on top of wlroots https://gitlab.freedesktop.org/wlroots/wlroots instead of going raw with DRM/KMS. Any folks that experienced wlroots?
Gonna have to create a binding for this one though, before I can start anything, but that will be hopefully a lot less work than dealing directly with DRM/KMS 😅
Stay updated with the latest network programming knowledge in #CSharp and #DotNet! 📚 Check out the new RSS feed for "Beyond Boundaries - Networking Programming with C# 12 and .NET 8" for tips, updates, and expert insights.
I have used the vk.xml registry & parsed the man docs to generate a complete Vulkan API with intellisense! 🚀
I took also the opportunity to add overloads in/out parameters, ReadOnlySpan/Spans and make optional params with default value. Lots of codegen, but that was worth it 😎
The vulkan_core.generated.cs is over 90,000 lines of C# code 🙈
Next step: Bare metal Vulkan C# NativeAOT on top of the Linux kernel + libdrm 😱
Just a reminder that if you'd like to promote continued development of JSON tech like #jsonschema#jsonpath and others in #dotnet, please consider sponsoring the #maintainers.
I've been noticing whole-machine slow downs whenever I heavily use my Dev Drive (for example, building source) that are just unacceptable.
A common example is I'll start a full build in Visual Studio and then go to type in Windows Terminal and everything I type will be delayed by multiple seconds. Even pasting will show only a few characters at a time.
I don't have anything against VS, but I just enjoy that we really make use of the available options, instead of being completely locked into everything Microsoft.
We build applications using .NET, Java and other stacks, deploy to Kubernetes on AWS, use Kafka, plus a bunch of other technologies, all working nicely together, without using everything from a single company. Love this!