A small s**tstorm is heading your way, if you're in the business of running code on Intel computers. Here's a sad story about the state of computing in 2019. It'll take a couple of tweets, but it's actually kind of important (?), so please retweet so this gets proper attention:
-
Show this thread
-
Replying to @damageboy
Is nobody attacking AMD, or is there some difference in design philosophy that has spared them from this wave of chip attacks?
4 replies 0 retweets 14 likes -
Replying to @geofurb @damageboy
This isn't a chip attack, it's a stupid design bug. That said, there *is* a difference in design philosophy. Intel has chosen performance over any kind of design sanity / safety, every time, it seems as a systematic rule. AMD hasn't.
2 replies 11 retweets 87 likes -
So while both AMD and Intel have been equally hit by the general idea of speculation-based leaks in userland code (nothing the CPU can do about that), Intel has also had a huge pile of massively privilege-crossing speculation leaks that AMD hasn't.
2 replies 2 retweets 25 likes -
But AMD and Intel weren't "equally" hit. Meltdown wasn't possible at all on AMD bc of their design. AMD has shown what it means to perform under the actual pressure of competition; they are more conscientious. Intel took shortcuts, cooked benchmarks and even threatened PC makers
1 reply 0 retweets 0 likes
"speculation-based leaks in userland code" = Spectre v1. "massively privilege-crossing speculation leaks" = Meltdown (and L1TF and others).
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.