Hacker News Reader

Comment by ziml77 | Hacker News Reader

I've been waiting for .NET 6 for the past year for the long term support. As much as I wanted to use .NET 5, I figured it would be best to only use LTS releases in production.

View on HN

not the best idea. because between .net 5 and .net 6 not a lot has changed. while 3.1 to 6 is waaaaaaaay more work than just 5 / 6 (which prob is just changing the version) especially on aspnetcore

I never run anything else than LTS in production. The in-between versions have basically been beta quality since .NET 1-preview.

Crazy how bing.com seem to not care for "beta" software :D

Bing.com developers are "first-party customers", they can raise issues internally, and these issues are prioritized

They literally don’t. They run actual preview versions in production to give the .NET team a chance to test new releases in high-traffic production scenarios. Though IIRC preview is a bit past beta ;)

Right… So if such a massive site uses it whats the excuse for the next CRUD app?

I don't agree personally. I've written production services in all versions from 2.0 up to 5.0, including the minor point releases and had no issues (especially most recently).

I know there have been some quality issues on the EF Core side, but on the Framework side everything has been pretty rock solid for me, with easy upgrades between versions.

Disclaimer: I work on .NET

What makes you say that? All versions of .NET - including non-LTS versions - have had an extremely high bar for quality before releasing.

I worked with all .NET versions. The most none-code related .NET bugs I had to hunt down in modern time has been in .NET Core 1.0 (clear leader) and .NET Core 2.2. The thing I like about the LTS versions is that they always work in and with any part of the ecosystem. Actually, one of our clients had to downgrade from .NET 5.

Disagree. .NET 5 and 6 previews have been remarkably solid+stable for me.

Reply on news.ycombinator.com