this post was submitted on 06 Jul 2026
342 points (93.0% liked)
Technology
86131 readers
3295 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Modern. Net is portable and fast, yes. But .NET framework is (mostly) not portable and it's tied to the version of Windows is on. We'll see when Microsoft decides to EOL it but so far it has not been announced. It's not getting more than security updates now, as far as I know.
We're converting everything we can (mostly web apps) to modern .Net (formerly core) so it can run on Linux. I may be stuck on Windows at work for the office apps, but my code runs on Linux.
Will never happen. The freaking VB6 runtime is still supported in Win11, and there's a mountain of .NET Framework code still out there.
Framework 4.8 still gets regular security updates, and will for years to come.
Yeah I'm not holding my breath. It will be around for a long time.
A couple of things I could see changing that would be a) Microsoft in financial trouble, b) AI both making it harder to keep up with security bugs, and making it easier to migrate away from legacy systems.
The chances of .net framework being among the first to go is slim though.
.NET Framework specifically - yeah. That's on life support. .NET Core is likely to be around for a long time. I spent the last few years at my former employer working on transitioning our server-side business layer components to .NET Core so they could run in Linux containers. Someone else got to deal with the Kubernetes aspect - thank goodness.
Now I usually avoid thinking about any of that. (Oops.)
Good call. I'm getting mired in the k8s side right now and we have dozens of small web apps that need upgraded and a couple beefier framework apps that need essentially rewritten. Unfortunately I can't escape lol.
We an ecosystem I overall like .net core and I agree it will stick around. I just can't wait to get off IIS and into Linux even if that means complicating things with kubernetes.
You wish.
Why bother? Just to keep paying MS?
What do you have to pay Microsoft for when using .NET?
Scalability was the primary reason. An application running on physical Windows-based servers can't quickly scale up and down, leading to higher hosting costs due to everything scaled to maximum capacity at all times. Or, more often, leading to slow performance and lost revenue due to the customer not wanting to pay for maximum hosting capacity at all times. So the customers want scalable cloud hosting. And when losing a customer often means a loss of millions of dollars in revenue for my former employer, they want to keep those customers.
A secondary goal is increasing the speed of deployment for new customers. Scripting the entire environment - including servers, network, storage - can make it very fast to spin up a new customer or testing environment. That can be done without .NET, of course, but .NET Core is the obvious next step for a large distributed enterprise product suite that is (was) already running on .NET Framework.
.NET Core isn't a primary platform for desktop or mobile client applications. It is very common as a hosting platform; that is likely to continue.