Dotnet 11 just dropped
Who cares about languages anymore, you just ask the AI to create something and it will use the best thing. Literally just forget about frameworks, libraries, languages, etc, and just trust the AI.
odd number, so not lts. not lts, so don't care.
>>110292768dotnet deez nutz
>>110292768my AI agent is very excited about that
>>110292768They vibecoded half of it. That's why it released before schedule.
>>110292905It almost certainly was vibe coded but they have been consistent in recent years about doing a release each November, with an even numbered LTS during odd years.
this has no usecase now that Go exists. Go killed it. it's now just playing catchup with Go.
>GOYnet
>>110292948go is like a magnitude less expressive than f#
>>110292800isn't dotnet lts 3 year support? Short enough to not care
>>110292948
>>110293014yes, but 10 -> 12 is one migration, 10 -> 11 -> 12 is double that.
>>110292897my AI agent is the new my wife's boyfriend
The new async runtime looks great, to be frank.
>>110293135the C# equivalent nowadays looks like this
>>110293125still a preview feature.not great to get opt'ed into preview features by just declaring your project as `net11.0`.
>>110293135You don't have to have an empty constructor, and you could use the primary constructor for the c # version.>>110293192No it's not, it's just not enabled by default.
>>110293199https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-11/runtime#runtime-async>Runtime Async is a preview feature. [...]>A net11.0 project no longer requires <EnablePreviewFeatures>true</EnablePreviewFeatures> to use Runtime Async.
>>110292768Based
>>110293061depends on how much work is required to update I guess. There is some nice shit in 11, like unions
>>110293047>b-but it's so simpl-ACKya, go is really bad. pretty much the only thing Go has over .NET CShart is native comp was the design from the start + gopls and toolchain tooling are less retarded and M$ coded.
>>110292768Yeah, let's force all programs written in our "language" to be rewritten every 2/3 years while offering no significant advantage. And people wonder why C is still in use...
>>110293199That's how to poo manager at Microsoft says to do it.https://devblogs.microsoft.com/premier-developer/go-and-csharp-comparison/
>>110292768Are we picking this up?
>>110292793Who cares about text anymore? Just ask the AI to write.
>>110293410cluelesshttps://learn.microsoft.com/en-us/dotnet/standard/net-standard>For existing code that targets .NET Standard 2.0 or later, there's no need to change the TFM to net8.0 or a later TFM. .NET 8, .NET 9, and .NET 10 implement .NET Standard 2.1 and earlier. The only reason to retarget from .NET Standard to .NET 8+ would be to gain access to more runtime features, language features, or APIs.
>>110293457Unless you need one of the new features, might as well wait until 12 comes out next November, as that's a LTS branch. Dotnet 11 also drops support for older CPUs like the Phenom II, so if your programs target a CPU that lacks CX16, POPCNT, SSE3, SSSE3, SSE4.1, and SSE4.2, you should stick with 10.
>>110293135I remember when I used to look at things like this (code) and read them with a sort of satisfying feeling, a colorful kind of excitement. I got a flash of that just now, for a mere split second. Anons....
>>110293191>School.Models
>>110292768Reminds me, I intended to look into F# this year (but muh AI, yeah, that can answer my questions). >>110293540Nostalgia hits us all.
>>110292768FFS busting my ass with current projects updating from 8 to 10.Also why is Windows afraid of 9?
>>110292948Usecase is legacy systems
>>110293661.net is almost a decade younger than go
>>110293661Unity: C#Godot: C#CryEngine: C#Stride: C#RE Engine: C#Hazel: C#Monogame: C#Evergine: C#Unigine: C#Unreal: C++yeah, legacy systems such as basically almost all videogames
>>110293690Kind of misleading since the .Net Framework, which current .NET is based upon, came out in 2002.
>>110292768Isn't this proprietary microslop garbage? Why use this if you can just have the shittiest ai write everything in rust now?
>>110293047This kills the toy project coder
>>110293954proprietary? no. but it does suck shit and is microslop garbage, so yeah fuck it.
>>110292768Literally who
>>110292793niggerbrain
>>110293954>Why use this if you can just have the shittiest ai write everything in rust now?Retard
>>110293539wish Rust would do this.having to set target-cpu=x86-64-v2 or 3 is stupid.
>>110293579
>>110293923You're based on your parents, but that doesn't make you 50.
>>110293954don't know.I find Rust tooling to be superior, by a lot, but if you are a cucked microslave, Visual Studio and .NET/C# is whatever.
>>110293923legacy software would be staying on .net frameworkhttps://learn.microsoft.com/en-us/lifecycle/faq/dotnet-core#i-am-using--net-framework-4-5-x-or-4-6-x--does-this-mean-i-need-to-update-my-application-to-work-with--net->.NET Framework versions older than 4.6.2 have reached end of support. If you are using the .NET Framework 4.6.2 or later, you are not required to update your application to work with .NET. That said, the .NET development platform offers several advantages over the legacy Microsoft .NET Framework platform and we encourage you to consider modernizing your apps to leverage modern .NET.
>>110293135>namespace wrapped in bracketsThats no longer a thing in C#
>>110293539They also improved performance, that's the main argument to jump into it.
>>110293954>Isn't this proprietary microslop garbage?Wrong https://github.com/dotnet/roslyn
>>110294039>muh tooling I am calling for total and complete web shitter death.
I hate this new trend of retarded extra-elongated letters>click on thumbnail...good fucking LORD
>>110294298letters aren't elongated. it's normal space grotesk.just messing with the kerning, the space between letters.
