[ComputerGuru]

The sheer amount of greenfield code being written today so dwarfs all the legacy code out there (especially that under consideration for upgrade) that Microsoft has just focused full steam ahead on the former. It’s hard to disagree with the business logic there.

(Medium-term migrations from ASP.NET MVC to ASP.NET Core, was more streamlined.)

[lacrimacida]

Yes, agree. But at the same time we could agree that microsoft left their older customers with a dead end solution costing a fortune or even imporrible to upgrade. They would be unwise to take microsoft recommendation again but corps seem to continue to do so..

[briHass]

To be fair, WebForms is 20 years old. It requires .NET Framework, but Microsoft just released another version (4.8.1) of that last year even though they said they were done with 4.8 back in 2019. By the time it's totally dead, companies will have been able to get a quarter of a century out of that tech.

That's outright amazing compared to any of the flash-in-the-pan JS front-end technologies. If you used the original AngularJS, for example, you got 10 or so years, and that's not an entire server-side framework.

[lacrimacida]

Yes, that’s somewhat sensible though that is true for many old tech… how many years have systems running powered by cobol by example?

[ComputerGuru]

I’m too busy being angry at Microsoft for abandoning SWF, WPF, and UWP without providing an amazing replacement to worry about how they treated webforms.