Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET 8

devblogs.microsoft.com

Post reply on HN
Print view View original

51–60 of 374 posts

Re: .NET 8

#51

Post by Thaxll »

financltravsty wrote: post #8

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

Big difference is that Go is stable and conservative, net core keep adding a billion features every release. Looking at some net core 2/3 stuff and now to see how many things changed.

Good luck with your code base in 5 years when someone decide to add all the new stuff.

Re: .NET 8

#52

Post by martindevans »

jordigh wrote: 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…

There used to be .NET Framework (which was a Windows only runtime built by Microsoft) and Mono (an open source implementation for various other platforms).

In 2016 they started building .NET Core which is new open source implementation (built mostly by Microsoft) which runs on more platforms. For a while all three existed side by side.

Eventually .NET Core caught up and overtook the other implementations. These days Framework is legacy. Core has been renamed to just .NET (since it's now _the_ runtime) and Mono (as far as I know) has been totally replaced by it.

This is all from memory, so apologies for any inaccuracies!

Re: .NET 8

#53

Post by meibo »

croes wrote: post #36
donny2018 wrote: post #23

Earlier quoted context omitted.

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.

This is not unusual in Microsoft-land. If a tech stack or version is very widely adopted or heavily revamped in a new version, they will often support that old version for a very long time - see Windows 7.

Re: .NET 8

#54

Post by ryanjshaw »

klauserc wrote: 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".

Kind of annoyed - I just spent the past week getting familiar with Dapr, and now there's Aspire which seems to have similar goals and is also funded by Microsoft: the Azure CTO even wrote the introduction to the Dapr for .NET Developers book!

And of course the Aspire announcement makes no mention of Dapr - I wonder if the teams have even spoken to each other!

Re: .NET 8

#55

Post by mathverse »

dodyg wrote: post #44
willsmith72 wrote: post #20

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.

Microsoft seems weird tho. They dont really support any recommended way to do .NET on Mac and you have to rely on Rider or half ass VS Code experience.

Re: .NET 8

#56

Post by mardef »

EspressoGPT wrote: post #12

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

It is confusing, but recently it's pretty straightforward

.Net framework is the OG .Net and is windows specific. That stopped at v5 (I think)

.Net Core is the cross-platform reboot that was mostly a subset of framework, but not a proper subset.

If you wanted to write a library that worked across everything, you would target .Net standard, which wasn't a framework itself, but the intersection of APIs that existed everywhere.

Today, framework is discontinued, which makes standard kinda moot, and they dropped the "Core" branding. So as of .Net 6, that's pretty much all you'd write for new code.

If you have legacy code, then yeah you're back in that quagmire

Re: .NET 8

#57

Post by nightski »

croes wrote: post #36
donny2018 wrote: post #23

Earlier quoted context omitted.

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.

Every even release is LTS (including .NET 8 today). New projects should not use Framework at all. It's really not confusing at all.

Re: .NET 8

#58

Post by viraptor »

pdntspa wrote: 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.

Not first-party, but AvaloniaUI is doing pretty well in the cross platform department.

Re: .NET 8

#59

Post by RajT88 »

xeromal wrote: post #4

Tangentially related but I was impressed with .NET recently. I was recently tasked with tackling an extremely old and proprietary video format that embedded GPS, video, audio, and several other components. The files were huge and just a mess to understand and I eventually found an old player application that was also proprietary. I decompiled it into C# and stripped the player aspect out of it leaving the code the pe…

The .Net ecosystem has a lot of great tooling, for sure.

The main issue I have had is if you are trying to get into the .Net Ecosystem without spending money. There are quite good free tools, but you have to figure out what works best for you if you're used to the non-free ones.

I assume instead of Reflector for the decompilation, you used DotPeek?

Re: .NET 8

#60

Post by SideburnsOfDoom »

mardef wrote: post #56
EspressoGPT wrote: post #12

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

It is confusing, but recently it's pretty straightforward .Net framework is the OG .Net and is windows specific. That stopped at v5 (I think) .Net Core is the cross-platform reboot that was mostly a subset of framework, but not a proper subset. If you wanted to write a library that worked across everything, you would target .Net standard, which wasn't a framework itself, but the intersection of APIs that existed ever…

> .Net framework is the OG .Net and is windows specific. That stopped at v5 (I think)

.NET Framework Stopped at version 4.8

That's why .NET (formerly Core) could pick up at version 5.0

Post reply on HN