Processors change? Non-sequitur. Spectre an its ilk arrived on the scene at least a decade after MS had developed a reputation for shipping shit code.

Libraries become deprecated or vulnerable? Non-sequitur. Whose libraries? Who deprecated them? Remember, this is a company that personified Embrace, Extend, Extinguish. If they picked shitty vendors for libraries and did no due diligence on that source code, why are the externalities foisted upon users? Also, libraries don't "become vulnerable" through some magical process. Either the bug was there from the beginning, or a shitty change was introduced and not caught.

Design paradigms shift? And this is an excuse for writing shitty code? I don't buy it.

New integrations require new code and that means taking into consideration the new shape of the system. Sounds like they did a really shitty job of that and they make it the user's problem.

Should we blame the old house builders for using asbestos? Unequivocally, yes. Those shitheads knew or should have known. Don't believe me? Here is a handy link: https://www.sciencedirect.com/science/article/pii/S0169500224003623

Do note the decades between when it was understood the shit was dangerous and when the decline as a building material happened.

So, no, MS still does not get a pass.

We should blame a shitty company for not being able to maintain their code.

Seriously if the world depends on some dumb company with some tiny number of people relative to the planet, then the world is dumb and fucked.

I see you have yet to meetmy old friend Debian, who was supporting i386 until 2 weeks ago, and includes a much broader library of softwate than Microsoft has ever maintained.

False dichotomy. That was a business decision with externalities foisted upon users.

Go ahead, bro. It's on CPAN.