Live data from Hacker News

.NET 8

devblogs.microsoft.com

11–20 of 374 posts

Re: .NET 8

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

Re: .NET 8

#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 binary format as .exe, where is the ".NET for hardcore open source Linux nerds" blog post?)

Re: .NET 8

#14

Adding spreading is neat, but curious why they chose to go the two dot route instead of three. It's been a while since I've worked in C#, so I can't remember if there are any reserved implications of three dots.

I think 3 dots is the varargs syntax so they didn't want to collide

Variable number of arguments is a keyword, params. I don't believe there's any 3 dot operator in C#. https://learn.microsoft.com/en-us/dotnet/csharp/language-ref...

Re: .NET 8

#15
post #6

Apart from the very welcome QoL features in C# 12 (collection literals, primary constructors for ordinary classes), the "Aspire" announcement is very interesting. Haven't decided yet if its a good thing or too much "magic".

I will start reading about it here: https://devblogs.microsoft.com/dotnet/introducing-dotnet-asp...

Re: .NET 8

#16

.NET 5, .NET Standard, .NET Framework, .NET Core, ... now .NET 8. It's so confusing still.

If you're doing any new work as of the past 3 years, it's just .NET. It's really not that confusing unless you're updating legacy software in which case you're probably quite embedded in the ecosystem already.

Re: .NET 8

#17
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…

[deleted]

Re: .NET 8

#18

.NET 5, .NET Standard, .NET Framework, .NET Core, ... now .NET 8. It's so confusing still.

I wanted to create an application. So apparently among the options are .net core blazor and MAUI blazor and their non-blazor versions. So many options with very confusing marketing.

Seems like others are confused too: https://www.reddit.com/r/dotnet/comments/pqi891/net_maui_app...

Re: .NET 8

#19

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
Post reply on HN