Can I get an explanation of the relationship between .NET and Mono? I have vague memory of reading somewhere that Mono or maybe just MonoBuild was completely obsolete since everything was now open source in .NET. Does Mono still have a reason to exist? Is it all incorporated into .NET now? (btw, I still don't get why it's called .NET, and I don't know if assemblies are native code or bytecode wrapped in the same bina…
.NET 8
41–50 of 374 posts
Re: .NET 8
#42I'd love to hear from some .NET fanatics, how would you convince someone to use that ecosystem over another?
Re: .NET 8
#43It actually addresses several warts (finally span pinning!), brings some new shortands, makes the syntax more uniform and comes with some performance improvements as well.
[1]: https://devblogs.microsoft.com/dotnet/announcing-fsharp-8/
Re: .NET 8
#44I'd love to hear from some .NET fanatics, how would you convince someone to use that ecosystem over another?
- New stuffs integrate nicely with existing features.
- C# and F# gets yearly updates.
- Somehow they manage to get the platform faster every year.
- Microsoft Orleans.
Re: .NET 8
#45.NET 5, .NET Standard, .NET Framework, .NET Core, ... now .NET 8. It's so confusing still.
Re: .NET 8
#46They link to "Announcing C# 12", but not a single mention of F# and "Announcing F# 8"[1], huh? (Edit: At least there's a link now.) It actually addresses several warts (finally span pinning!), brings some new shortands, makes the syntax more uniform and comes with some performance improvements as well. [1]: https://devblogs.microsoft.com/dotnet/announcing-fsharp-8/
Re: .NET 8
#47Lots of very cool stuff here (AOT, Aspire, etc.). .NET has been held down by the image of its early days, but it has become a pure joy to work with recently. The improvements in tooling and ergonomics have made it a replacement for Go in our org (we migrated from .NET Core 3.1 to Go back to .NET 6 recently).
Re: .NET 8
#48I just wish its cross-platform UIs weren't such a mess. Particularly with its MVCish implementation, it was like it couldn't decide what it wanted to be. I really really wish there was a good, straightforward desktop GUI for .Net that simply worked crossplatform and wasn't a complete pain in the ass to program.
Re: .NET 8
#49Lots of very cool stuff here (AOT, Aspire, etc.). .NET has been held down by the image of its early days, but it has become a pure joy to work with recently. The improvements in tooling and ergonomics have made it a replacement for Go in our org (we migrated from .NET Core 3.1 to Go back to .NET 6 recently).
Re: .NET 8
#50Lots of very cool stuff here (AOT, Aspire, etc.). .NET has been held down by the image of its early days, but it has become a pure joy to work with recently. The improvements in tooling and ergonomics have made it a replacement for Go in our org (we migrated from .NET Core 3.1 to Go back to .NET 6 recently).
With consistent, reasonable-by-default threading abstractions baked in