They are working as designed. There was a choice between speed and security, and they chose speed. That was what the consumer wanted. Now security is becoming ever more of a focus for people, so that decision seems like a bad one.
Not in the creation of hardware. Security tends to be a software level concern.AFAIK, there was no choice made - it was later found that an exploit was possible. It's not like someone thought through the possibility and then decided to ignore it in favor of speed.
Security has always been a major concern; it's fascinating to see all the security implementations that this exploit can bypass.
People don't realize how true that is. It is getting to the point where anything that uses a computer is never truly secure.nothing connected to the internet is ever completely secure, nor likely ever will be
Not in the creation of hardware. Security tends to be a [STRIKE]software level concern[/STRIKE] [post-exploit afterthought].
Average consumers will notice little difference. The "fix" stops the processor from guessing what will happen next and peeking at memory addresses to look at the contents. If the processor was a good guesser at the workloads it was doing then there will be a performance loss when this functionality is removed. If it was bad at guessing then no performance loss will happen. I doubt this will be big news except in specialized cases.You're talking millions of p***ed off people and billions of dollars in potential litigation liability. Ain't nobody going to admit nothing if they want to keep their job
As much as a 30% hit in speed in some applications! It will be pitchforks and torches
Not in the creation of hardware. Security tends to be a software level concern.
Sweet. Except for making the cost of straw go up in the future.