If you start developing a new software today, it won't need to run on those computers. And if it's old enough that it need to, you can bet all of those architectural decisions were already made and written into stone all over the place.
> If you start developing a new software today, it won't need to run on those computers.
This is a weird argument to make.
For context, I work on mesh overlay VPNs at Defined.net. We initially used Unix domain sockets for our daemon-client control model. This supported Windows 10 / Server 2019+.
We very quickly found our users needed support for Server 2016. Some are even still running 2012.
Ultimately, as a software vendor, we can't just force customers to upgrade their datacenters.
It’s actually the opposite of Microsoft quickly eoling on the server side. Server 2012 was EVERYWHERE as late as 2018-2019. They were still issuing service packs in 2018.
If you start developing a new software today, it won't need to run on those computers. And if it's old enough that it need to, you can bet all of those architectural decisions were already made and written into stone all over the place.