What an absurdity!
Forcing your software to circumnavigate the hardware bugs, just so they can keep selling them with a 'cheating' speculative execution engine. Yes, it’s cheating. It’s running all the red lights. That’s why it’s so efficient.
Guess what? You are paying triple by circumventing this in software, which makes the whole thing even slower. Yet, Intel keeps publishing benchmarks WITHOUT mitigations enabled; something that should be illegal to begin with.
They are trying to make this look as if something immensely complicated has a few bugs. Shit happens, right? Wrong. This is a fundamental problem. It’s not that they didn’t know they were ignoring the red lights. They simply chose to do so, because cheating can be lucrative. Remember Volkswagen with their "super clean" cars? How did they manage to get them that clean again? Oh yeah, just like Intel managed to get their crappy processors so fast...
You may throw in "But what about the competitors? Didn’t they cheat as well?" Again, just like Volkswagen. The competitors (not all of them) had to follow. It was either that or make it public that they were cheating.
Here’s some insider information for you: With Volkswagen, they tried to make it public since 2007 without avail! Only when a US secret service thought that it was time to punish the Germans, it made the headlines and went to court.
With Intel, it’s the other way round. German "intelligence" is behind "rendering those bugs public" (revenge) and the US is backing Intel. Hence, no refunds and let’s pretend that those "bugs" are unavoidable.
I wish the (compiler) programmers had the guts to refuse, simply telling them that the hardware needs to be replaced.