Agreed. The FUD is trying to ascribed blame for this - there is no blame to be ascribed here for the vulnerabilities themselves.
Anything else (responses to / lack of responses, badly-coded stop-gap measures, the not-so-very-innocuous sale of corporate stock) - yeah, all those can have fault attributed to them to any one person or group or corporation. But trying to hold anyone liable (not libel
) for the vulnerabilities themselves is ludicrous at best, and, really, utterly ridiculous.
But Josey makes a point above me - I'm also in a similar situation - my CPU controller Chipset family, the X58, was developed over 10 years ago. It was first released later that same year.
I purchased my board in mid 2011, after lightning took out my then current machine, and being a Master's student with already 1 year of data for my thesis gathered, I needed to build something quickly. I'm still using that same motherboard, CPU and RAM (and case) as my daily driver, the one that runs Insider builds, and VMs (every other component is newer - except possibly the Blu-Ray burner - I honestly don't remember anymore).
The last BIOS released for that machine was released before I even bought it. On top of that, one of the team engineers at eVGA has specifically stated that this (and other older 'legacy' family boards are awaiting BIOS source code directly from Intel in order to issue an update).
https://forums.evga.com/FindPost/2749683
Until that happens, I am pretty much .... out of luck. And others with legacy boards like this (and even much, much newer boards, I've already started hearing rumors of boards as new as 4 years old are being denied any new BIOS / UEFI updates) in pretty much the same boat, well, you can see how it's rather hard to take your advice at just face value and have everything patched - because, well, we really can't have everything patched.
So, it would truly be nice if Windows forced a microcode update via Windows Update to our machines because, at this point, Intel is probably not going to provide BIOS source code from 5 years ago, let alone 10....