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