.Net has changed significantly since WebForms ASP+ backend... MVC reshaped things and this has been refined, Core -> 5+ has also changed things a bit... it's not like it's the same code you worked with two decades ago.

Except that most of the same code keeps working, and even between classical Framework and Core, most concepts keep working even if the APIs, and configuration files, are a bit different.

One can keep doing MVC just as always, no need to jump into Razor Pages with code behind, or the minimal APIs designed to cater to JS devs.

Just like JakartaEE isn't fully 100% Java EE, yet most stuff works the same way.

The point is, you wouldn't normally start a .Net project today the same as you would in 2002. Personally, I jumped to separate html+js and using ashx until MVC came out, because WebForms was a mess. In the end, it's not like it's the same, even if a lot of the same code might work (unless you're using WCF or many other things that broke along the way).

It is still the same framework, and most stuff still works.

Web Forms is deprecated since around 2010, while 12 years old MVC is a matter of creating a new .NET Core project, even WCF is now mostly supported on CoreWCF as Microsoft has forced to support it.

Windows developers don't like Python 2 vs Python 3 experiences, and have voted multiple times when Microsoft tries to play Apple.

This is hardly like FE frameworks having been doing since jQuery.

Comment last week during a PR, why are we still using webpack instead of XYZ.

So, you've taken a project from 15+ years ago in .Net and run it in .Net 6+?

You can run JS from 15+ years ago in the same vein.

Not because contrary to the npm junkyard, the ecosystem values stability.

Thankfully only have to deal with JavaScript on the browser.

So after touting something you can do, you've never actually done it.

I have had to touch. Net code that hasn't been updated in years and bring it current. It isn't fun.

By the same token, I lost about a week and a half recently updating a front end project that was started about 5 years ago.

I'm either case, .Net is definitely not the panacea you seem to assert that it is.

.NET and Java definitely are when compared against many fashionable alternatives, naturally you can come up with corner cases like projects using remoting or RMI, while ignoring their ecosystem stability versus those alternatives.

It is still MSBuild, Maven and Gradle after all these years, three major IDEs, most libraries just work, there are hardly talks about why we are doing it all wrong and use framework XYZ or build system ABC instead and so on.

I actually can't wait to get my hands on .NET after years of developing my backends in JS and Python. I've read the docs, watched some tutorials and played around with code, and it looks and feels dope. To be honest, for smaller projects I will probably continue to reach out for something JS. But for anything more serious I will be using .NET Core.