What if CPU speeds haven't plateaued, but instead all the extra clock was being used to help the intelligence agencies fully monitor our computers?
This would be a copy of how power plants underreport their capacity and use the excess to rapidly evaporate steam to create the weather.
I am beginning to think all the other CPU security flaws over the years were red herrings to throw us off of this one.
We need to be scanning all our executable code for instructions that turn on and enable the deep core. Or at least the eggheads who know how to do that should do that.
No, there is a hidden instruction in A VERY SPECIFIC LINE OF X86 PROCESSORS FROM A SINGLE COMPANY MOST OF YOU HAVE NEVER HEARD OF WHICH THE AVERAGE USER IS VERY UNLIKELY TO BE ON.
Jesus fucking christ you niggers make searching for security information extremely difficult. BE ACCURATE!
you know he's completely uninformed on the subject and just going in with a hammer?
there are tools to debug and reverse engineer cpus
study guide:
silicon compiler
verilog
VHDL
DARPA
microscope
blackboxed electronics
osciliscope
stop being stupid there's no reason for this where he is
That started happening around sandy bridge with the intel ME you faggot. It's like javascript bitcoin miners but for the A.I by using your CPU. If you disable the ME your battery life skyrockets with all the idle time you get on a optimized software system like lubuntu or gentoo. Like I got 5+w of idle savings just by disabling ME.
Believe that Intel emulates x86 behind 128 synchronized instructions that must be carefully chosen to also create a valid cryptographic hash when salted with the current system timestamp and a hardcoded secret prime instead of toggling this mode with one undocumented instruction. Have faith. Pray.
The better question is what the fuck is actually under the x86 emulation layer.
CPU speeds started rolling back when engineers worked out that pipelines with 30 stages aren't actually that good. Its better from a performance standpoint to have a shorter pipeline which runs at a slightly lower clock than the opposite.
It's about the fact that it is implemented in something in the first place.
Which makes it more likely that it exists in other products as well.
It's like a world in which ebola only existed in theory. But then in some nigger village you find a nigger with ebola.
You now know that both ebola exists, and that some other villagers are likely infected as well.
it's several megabytes of javacsript running in the background + poorly optimized html5 media players