3 ms·
It's a good question and I bet there's going to be a lot of speculation and pointing to documents and people that predicted these issues years ago. But it's imp
by maltalex 9y ago
It's a good question and I bet there's going to be a lot of speculation and pointing to documents and people that predicted these issues years ago. But it's important to remember that hindsight is 20/20.
All of us probably have, on some level, risky behaviors we participate it. Maybe you're reusing a password between a few of sites, maybe you're driving a little bit too fast sometimes, or maybe you're sitting at your computer a bit more than you should. We take these risks daily, both at home and at work. Risk is a fact of life and of business.
Most of the risks we take turn out OK for us. But some don't. The problem is we tend to ask "why didn't we foresee it" only when something goes wrong, regardless of whether that risk was worth taking at the time. So the question is incredibly biased. Risks don't exist in a vacuum.
Anyway, I'm not an expert on CPUs or the CPU industry, but for what it's worth I'm guessing that they knew that there was a theoretical way to exploit this architecture. Maybe they knew how bad it could be, maybe they didn't. But market forces today are a lot stronger than some theoretical problem that may or may not happen in the future, especially if that theoretical problem would also hurt your competitors. I bet that fixing the problem is expensive in either money or performance. If that's the case, then fixing it when the risk is theoretical could be a bad business decision and might give your competitors an advantage (cheaper or more performant hardware).
I think that a much more interesting question to as is how do we incentivize this industry to avoid these types of problems in the future
- Top19 9y agoYou make a good point. Sometimes trying to prepare for a crisis that might never come is the worst strategy. Supposedly, this is what makes democracies stronger than authoritarian governments. Democracies argue endlessly, never taking action until a crisis, and then pulling off the impossible. Authoritarian governments will try some crazy engineering solution for a problem they really don’t have (like irrigating Kazakhstan), and then 15 years later 90% of the Aral Sea is gone. In other cases, preparing for Y2K, although it didn’t come, was actually extremely useful in responding to the attacks of 9/11. A lot of protocol that was used that day was originally going to be deployed 18 months earlier during New Years, December 31st, 1999.