Live data from Hacker News

.NET 8

devblogs.microsoft.com

31–40 of 374 posts

Re: .NET 8

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

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

There is not and wont be. MS will commoditize apps to bake as many features as possible as fast enough as possible using some bastardized Electron crap.

Re: .NET 8

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

In olden days .net was Windows only. Mono was an independent effort to build a cross platform runtime. With .net core MS made it open source and cross platform. They also bought Mono but that is more or less abandoned I believe latest versions of .net run well on Linux and Mac and now also in browser. They have also dropped Core from the name and there is only one .net which is open source and cross platform.

Edit: seems some part of Mono still live.

Re: .NET 8

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

One reason is that Mono supports a bunch of minor platforms [0] that .NET doesn't - yet (for example, FreeBSD support has an active Github issue [1]... although it's been active for _eight years_).

If you're running Windows, Mac, or Linux I'm not aware of major reasons to use Mono.

[0] https://www.mono-project.com/docs/about-mono/supported-platf...

[1] https://github.com/dotnet/runtime/issues/14537

Re: .NET 8

#36

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

Starting from .NET 6 I think, it's pretty consistent. It's just .NET 6, 7, 8, etc.

Still confusing if can't simply switch to the most recent version or have legacy software.

.NET Framework 4.8 will be longer supported than .Net 5, 6, 7 and maybe 8.

Re: .NET 8

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

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

Mono is still used by Unity, and by .NET MAUI for their iOS and Android implementations. https://learn.microsoft.com/en-us/dotnet/maui/what-is-maui#h... . For most .NET apps you can use .NET 5/6/7/8.

Apparently .NET MAUI iOS target can run on NativeAOT[0] instead (with better performance and smaller binary size) but I'd expect it to be a bit unstable experience for now since it's very new.

[0] https://devblogs.microsoft.com/dotnet/dotnet-8-performance-i...

Re: .NET 8

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

.NET used to be Windows-only. Mono was a cross-platform implementation of .NET done by a third party and not by Microsoft.

Microsoft eventually created .NET Core, their own cross-platform implementation of .NET, which eventually became .NET 5, 6, 7, and now 8.

Mono should not be used for new projects. .NET 8 is vastly superior. Mono is only still used for things like Unity who have decided to not or slowly migrate off of Mono.

Re: .NET 8

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

Avalonia + FuncUI (for a MVU design) seems to have a lot of fans.
Post reply on HN