Re:What's new in the .NET 11 runtime
by SurajMishra on Tuesday November 10, 2026 @09:20AM
(#50440764)
So for a requirement where both golang and .net would suffice, would you choose .Net over golang?
Yes. Unless I really need CSP, but then I would much rather use f#+hopac because CML is the bee's knees.
For general concurrency where async doesn't suffice, go is nicer than C#, but hopac is nicer than go.
If go had proper concurrentML I am pretty sure I would use go a lot more. Again: this is for hobby projects where I get to choose freely.
Re:What's new in the .NET 11 runtime
by abstractcontrol on Tuesday November 10, 2026 @12:01PM
(#50443083)
Based Hopac enjoyer. I built the Spiral's language server using it. I have to admit though that these days I just use native .NET channels for all my message passing needs.
I vastly prefer cml, but hopac has a lot of missed opportunities. I vibe coded my own language on top of c# that has a cml that is much more integrated with the language (and no other constructs are available :)). Being able to use events for things like reading from ports, so that you can select over reads and only the winning read actually takes anything from the port is more than nice to have. Or having STM that can be run as an event, so that you can choose over a transaction or a timeout in extreme congestion. Since it is composable, you can abstract away a lot of the details behind simple function calls.
I am kind of curious if it becomes faster when moving to dotnet11.
I have also found c# async to be lighter than go's concurrency story, and dotnet11 is going to make that much more clear.
Now: I write software for fun, not for money.