Live data from Hacker News

.NET 8

devblogs.microsoft.com

141–150 of 374 posts

Re: .NET 8

#141
post #51

Earlier quoted context omitted.

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.

.NET is stable, they very rarely remove things. Code written for .NET Framework 2.x will probably work fine on .NET 8 (unless it uses the things that didn't make the jump, like WCF, but there are libraries that provide SOAP support.) Can a single developer remember all of .NET? No, but that applies to most languages/ecosystems. But if you encounter something you've never seen, you can always check the docs. And the t…

> Code written for .NET Framework 2.x will probably work fine on .NET 8

WebForms would like a word.

Re: .NET 8

#142
post #103

Earlier quoted context omitted.

Yes, it has all that - console applications with no GUI, GUI interfaces on the desktop as well as web interface - has pretty much everything if you know where to look.

And Visual Studio is probably one of the best if not the best IDEs out there.

Maybe it has gotten better. I found it way too much, but then I am writing Python in Notepad++. All I saw was far too many options and an assumption that you were Writing At Enterprise Scale.

Re: .NET 8

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

.Net 8 is supported 3 years, . Net Framework 4.8 presumably longer.

Confusing.

Re: .NET 8

#144
post #103

Earlier quoted context omitted.

Yes, it has all that - console applications with no GUI, GUI interfaces on the desktop as well as web interface - has pretty much everything if you know where to look.

And Visual Studio is probably one of the best if not the best IDEs out there.

If you're willing to run Windows.

Re: .NET 8

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

UI frameworks are a heavy lift, more-so to be cross-platform. Let's say someone tries, but it's not to your liking? I mean, there can't be 12 different frameworks, that's not sustainable.

I am really flexible in terms of a toolkit's ergonomics. But I am running into situations where things just straight up don't work (Java/graalVM), or that I need to implement some really basic interaction and there is no guidance in the documentation and the abstractions don't make any sense. (Avalonia)

And that's assuming it even compiles or packages.

So far the only winner has been QT (via pyside6 for me)

Re: .NET 8

#146

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

> .NET has been held down by the image of its early days, but it has become a pure joy to work with recently People have been saying that for the past 4 years. As someone who's never used .NET but develops embedded apps for Linux, I had high hopes for it become the best story for crossplatform development, it still feels like the crossplatform is held by ductape. It's still Xamarin for mobile, Avalonia (a 1-man proje…

MAUI is built using WinUI. It is same platform.

Re: .NET 8

#147
As full stack .net dev, I am so disappointed every “who is hiring” thread. I would be game to join a trendier group of like minded devs but if you get one .net posting you are lucky, and it’s most likely rockstar.

:(

Re: .NET 8

#148
post #89

Earlier quoted context omitted.

I think the parent comment is talking about System.Threading.Tasks. I might be wrong though.

Oh, I see. I was hoping for something new. I keep on hoping some sort of BEAM-like (from Erlang) process gets added to .NET.

It was tried and the dotnet team decided to drop it: https://github.com/dotnet/runtimelab/issues/2398

Re: .NET 8

#149

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.

We gotta be. We know Microsoft isn't gonna be :D.

Re: .NET 8

#150
post #81

Earlier quoted context omitted.

Have a look at Blazor Hybrid. This is really nice thing. Blazor is the first UI toolkit I actually love for many years.

I have. Too much "magic," and I'm too experienced to fall for that again. No more magic, I should be able to see and understand how every part of my stack works top to bottom. That's why I'm for isolating the front end from back end frameworks via something agnostic like WebAPI.

With blazor wasm you generally do have separate project for front end and api.
Post reply on HN