Live data from Hacker News

.NET 8

devblogs.microsoft.com

71–80 of 374 posts

Re: .NET 8

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

.NET 7? There was no monetizing in it. If you want to look somewhere, look at the C# DevKit for VS Code.

Re: .NET 8

#72

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

Nice, although I'm mostly concerned about the fact that they didn't bother to mention it. I know it isn't too popular, but it's still a part of the toolchain and not in maintenance mode like VB.NET is.

Re: .NET 8

#73

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

You can make a fully functional API service with minimal or no third party dependencies.

Re: .NET 8

#74
post #59
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?

I've used ILSpy instead of JetBrain's tools for this.

If you're a real OG, you used `ildasm`.

Re: .NET 8

#75
post #36

Earlier quoted context omitted.

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.

Yes, but that parent has a point: that new LTS is 3 years of support. Which is not that "long term".

We're on .NET 6 now, because it's LTS. But as of today, it has 1 more year of support (1)

.NET Framework 4.8 as an OS component, is actually supported for longer - no end date given (2).

Note that .NET Framework 4.6.2 is supported until Jan 12, 2027 - that's longer than .NET 6 and 7, and maybe 8

1) https://learn.microsoft.com/en-us/lifecycle/products/microso...

2) https://learn.microsoft.com/en-us/lifecycle/products/microso...

Re: .NET 8

#76
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!

Yeah, my confidence is also low. This looks like Dapr all over again.

Re: .NET 8

#77
post #50

Earlier quoted context omitted.

With consistent, reasonable-by-default threading abstractions baked in

Are those new? What are they by name?

I think the parent comment is talking about System.Threading.Tasks.

I might be wrong though.

Re: .NET 8

#78
post #44

Earlier quoted context omitted.

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

You're right. They did until recently, but it was bad. Now they seem to have moved attention to creating a great experience in VSCode but some of it may require a MSDN sub (they seem to be making the core experience free, with paid extensions to give more Visual Studio-like features in VSCode).

Re: .NET 8

#79

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/

One of the first comments on the site points out this lacuna. Leave it to the F# community to be vocal about this.

Re: .NET 8

#80
post #44

Earlier quoted context omitted.

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

I believe that vs code is the way they want you to do .net on windows as well.

The tooling is all CLI based anyway so do what feels best. :)

Post reply on HN