Live data from Hacker News

.NET 8

devblogs.microsoft.com

41–50 of 374 posts

Re: .NET 8

#41
post #13

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…

The answer is complicated, that's why. In a good way kinda - you can build IL bytecode exes that are portable across all platforms and you can also build fully native platform specific binaries too (though there can be gotchas around library support).

Re: .NET 8

#42

I'd love to hear from some .NET fanatics, how would you convince someone to use that ecosystem over another?

I'm not a fanatic, just a long time user. The tooling and the documentation are superb. Plus the really long term support of everything. You can still compile and run applications that were build 20 years ago, even more.

Re: .NET 8

#43
They 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

#44

I'd love to hear from some .NET fanatics, how would you convince someone to use that ecosystem over another?

- It is a mature platform with yearly updates.

- 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

#46

They 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/

There is a separate post on HN :) https://news.ycombinator.com/item?id=38265390

Re: .NET 8

#47

Lots 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).

I just starting using .NET professionally very recently and coming from Go and Java a lot of the .NET platform is just downright pleasant.

Re: .NET 8

#48
post #11

I 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.

I would say Blazor is really very very good now. One of the most awesome things about it is that your skill with it transfers almost directly between a desktop app, web API, or web site. All the code is almost the same.

Re: .NET 8

#49

Lots 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).

At least until it gains an immense market share and Microsoft starts monetizing it again. They've already tried in .NET Core 7, no? I'm staying away for now.

Re: .NET 8

#50

Lots 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

Are those new? What are they by name?
Post reply on HN