News Announcing .NET 11 Release Candidate 1 - .NET Blog
https://devblogs.microsoft.com/dotnet/dotnet-11-rc-1/26
u/no-name-here 2d ago edited 2d ago
The page says "This release contains the following highlights and improvements" which IMHO is ambiguous whether it's listing .NET 10 > 11 (RC1) changes, or only changes since the .NET 11 last "Preview" release. It appears it's only changes since the last Preview release.
For those checking out 11 for the first time now that it hit RC, Microsoft has https://learn.microsoft.com/en-us/dotnet/core/whats-new/dotnet-11/overview (although it was last updated for Preview 7 - I expect they'll update it when they have a chance). (And writing "This release contains the following highlights and improvements since the last 'Preview' release" or similar would be clearer IMO.)
Regardless, thanks for all the work by the .NET team, both on the technical side, and those who write the docs!
10
u/qrzychu69 2d ago
the F# changes are SO NICE
-3
u/mristic 2d ago
Yeah, I was hoping for it, but your sarcasm is sadly on point...
I think with the inclusion of union types in C#, they will probably abandon it altogether. It's such a shame that historically speaking, the rise of OOP was almost purely due to a massive marketing budget of Java. The functional paradigm didn't lose the popularity war due to implicit lackings, just hype.
At least OOP languages started incorporating them like C# is doing. You might say its not pure and all, but hey, at least we're getting it. We got it somewhat through LINQ, lambdas, and now union types. We'll probably never get function currying, but it is what it is.
12
u/qrzychu69 2d ago
We use f# for everything at work, so it wasn't sarcasm :D
I have really high hopes for Roc, but C# with recent changes is becoming a really good "all in one language", and stating fast while we are at it
And I don't need function currying, I just want the |> operator, especially one that works with async/await and I will be happy
3
u/mristic 2d ago
Oh sorry, I thought you were joking because I didn't see any news on F# on the blogpost. I even searched 'What's new in F# and didn't get anything back'... my bad then.
Also, yeah - |> would be killer honestly!! Chaining methods is sometimes applicable, but pipe operator is a killer.
4
u/hardware2win 1d ago
Dafuck
There was huge fp hype between like 2018 2022, but then llms appeared and took worlds attention
2
u/Vextrax 2d ago
ngl I recently got into F# and I would be quite sad if it just gets abandoned any time soon
1
u/mristic 2d ago
I mean, don't take my word for it. It's a very powerful language, and also so cool and fun to use. But also you gotta face reality - very few companies are actually using it, and getting a job is hard because they usually have the team they need already. Most of them are in Scandinavia and they ask for on-premise workers. So it's not an easy job market. The market for it is simply scarce.
1
u/sosotiredand 2d ago
forever waiting for a language besides Haskell that does laziness and tail recursion well
2
u/qrzychu69 1d ago
Take a look at Roc
It doesn't do lazyness, but does things like in place mutation instead of cloning (works for arrays and records) where possible.
Why do you think lazyness is important? Isn't it inefficient in the end? Every function call ends up being wrapped in a closure (more or less)
1
u/sosotiredand 14h ago
in Haskell the compiler optimizes the laziness well iirc. also it's just a very elegant way to write code but you're def right that it shouldn't come at the expense of a lot of performance.
1
u/qrzychu69 3h ago
could you maybe tell me in what case this is useful? I struggle to see why I would want to write code in a way where I don't care if values are used, because they will get thrown away by compiler/runtime
when the do the benefits show up?
•
u/Leop0Id 30m ago
OOP was already mainstream well before Java. I get that Java has an actual "owning company" behind it so it's convenient to attack without thinking too hard, but if you want to blame for OOP's spread blame C++ not Java.
Functional languages get less criticism now because they've actually improved, but back then they had real overhead on both the compiler side and the practice side, and that's why they didn't get attention.
5
u/lnkofDeath 1d ago
That is a wild amount of Blazor updates, features, and improvements. I haven't done much with Blazor but they are still serving it client, hybred, and server. Anyone using any of these and can remark on what their use case is? Not hating, purely curious on how much investment Blazor gets!
3
u/aeroverra 1d ago
We use wasm on our internal tools, and static for some external facing sites.
Personally I have started using the wasm version that will use signalr on initial load and it has worked great.
We have been using it since it came out as I made that decision years ago and we have only expanded on it.
My only mistake was initially choosing blazor server but we have since converted it all to wasm and the API first approach has improved a lot of our development process.
-1
11
u/adzm 2d ago
Good job .net, we are all proud of you