Like the fact that there's no AI whatsoever. There are limited-purpose algorithms for very narrow tasks which work a lot like the calculator: i.e. they far surpass what the average human being is capable of (most people cannot compute in their heads), yet they cannot reason (which is why image recognition systems can be easily fooled), think (which is why proper translation is a pipe dream) or invent anything (which is why they cannot come up with new ideas). The hype about AI is so strong, people actually fear will be enslaved by robot overlords soon yet we are not close to general AI than we were 50 years ago, we just have much better hardware to use to train those algorithms.
Even image recognition AI which is touted as a breakthrough is largely incomplete because animals intelligence doesn't require petabytes of data and petaflops of compute power to recognize objects in all their embodiments maybe because we've deciphered only the outmost layer of the nervous system.
In short there's no AI to speak of. Up to this day we've just been automating the most primitive tasks which don't require intelligence per se. They require statistics, lots of data and lots of compute power.
Oh, and these algorithms are almost completely opaque, so we cannot understand them, properly tune them or even expect proper answers from them all the time.
Nice catch, however, to be honest, you're talking about possible ramifications, not about direct modification of the RAM which your process/application shouldn't get access to.
Those workloads with significant performance losses are more or less completely artificial, e.g. average users don't create hundreds of thousands of files day in and day out and even in this case only SSD disks are affected. Considering that SSD disk operations are sometimes several orders of magnitude faster than those for spinning disks this performance loss is still nothing to worry about.
I guess they won't be affected unless your application reads and writes data from/to the disk one byte at a time. People have already run network tests and the KPTI patch has a minimum performance loss.
I wonder if large corporations have any notion of conscience because the Intel ME fiasco is just too fresh in our memory to make such outrageous claims.
I like how they've weaseled out of the whole fiasco (why didn't/. post a link to the original press release?):
"Contrary to some reports, any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time".
I'm not sure I can read between the lines properly but I guess new revisions of Coffee Lake/Kaby Lake/SkyLake(X) CPUs are coming and they will contain a hardware fix (though it still seems highly unlikely considering how difficult it's to deploy a new hardware design - however unlike other fabless companies, like AMD/NVIDIA/ARM/etc Intel has everything under control). After all they've known about this issue for almost half a year.
Meanwhile as for consumer workloads they are correct. TwoGerman websites have already tested a Windows build with a fix and found very little performance losses.
Phoronix has also run a number of tests on Linux and found out that only few (mostly artificial) tasks are seriously affected.
Intel home users may sleep well. As for enterprise customers no one has run virtualization tests yet though - that's what truly important for large deployments (clouds).
I'm inclined to believe that Edge's advantage comes from its ability to utilize [GPU] hardware acceleration better and not from cheating on Microsoft's part.
I'm curious how much Cannon Lake and Ice Lake CPU architectures are going to be delayed. Since Cannon Lake is basically SkyLake on a 10nm node, Intel cannot release it with such a glaring hole which causes such a significant performance loss.
I've been running a Sandy Bridge CPU for seven years now, and now I'm really looking forward to the second gen Zen CPUs. Viva, competition. I'm really glad AMD is still around.
The developers behind the GRSecurity project measured up to 63% performance loss. If most common tasks are equally affected, Intel is sure fucked. Home users might not need to bother, but large cloud providers might be seriously affected.
Meanwhile the Linux kernel has received the largest incremental minor patch in its history (229KiB) - perhaps kernel 4.14.11 already contains all the required fixes.
I have a sneaking suspicion Intel shares will fall through the floor in the next few weeks because Intel CPUs might have suddenly become quite slower than their AMD Zen based counterparts.
He understands he's indirectly responsible for the killing and he's ready to serve jail time (just not a life sentence) if he gets caught (he's already been apprehended).
Livingston didn't say if the man, who was 28, had a weapon when he came to the door, or what caused the officer to shoot the man. Police don't think the man fired at officers, but the incident is still under investigation, he said. The man, who has not been identified by police, died at a local hospital.
Your fears are totally warranted as the new UI looks like modernshit we are already forced to consume in other OS'es like Windows 10.
Hopefully the new Thunderbird will be themeable but I wouldn't hold my breath considering that theming was essentially killed in Firefox (we can only apply a background image to its bars - that's it).
Slashdot Mirror
Just tested the sample exploits against uTorrent 2.2.1 build 25302 - none has worked.
Like the fact that there's no AI whatsoever. There are limited-purpose algorithms for very narrow tasks which work a lot like the calculator: i.e. they far surpass what the average human being is capable of (most people cannot compute in their heads), yet they cannot reason (which is why image recognition systems can be easily fooled), think (which is why proper translation is a pipe dream) or invent anything (which is why they cannot come up with new ideas). The hype about AI is so strong, people actually fear will be enslaved by robot overlords soon yet we are not close to general AI than we were 50 years ago, we just have much better hardware to use to train those algorithms.
Even image recognition AI which is touted as a breakthrough is largely incomplete because animals intelligence doesn't require petabytes of data and petaflops of compute power to recognize objects in all their embodiments maybe because we've deciphered only the outmost layer of the nervous system.
In short there's no AI to speak of. Up to this day we've just been automating the most primitive tasks which don't require intelligence per se. They require statistics, lots of data and lots of compute power.
Oh, and these algorithms are almost completely opaque, so we cannot understand them, properly tune them or even expect proper answers from them all the time.
Last time I checked a complete rewrite is not necessary at all. Sometimes a one liner, e.g. SetDllDirectory(""), is more than enough.
Neither ;-) I don't even understand why you got such an impression. I was honest and unbiased.
Enough with speculation. All the details have just been revealed:
Source: Reading privileged memory with a side-channel
Website: Meltdown and Spectre
AMD CPUs are susceptible to one of the attacks.
You don't have to wait for a patch. Kernels 4.14.11 and 4.15-rc6 already contain the fix.
Nice catch, however, to be honest, you're talking about possible ramifications, not about direct modification of the RAM which your process/application shouldn't get access to.
Those workloads with significant performance losses are more or less completely artificial, e.g. average users don't create hundreds of thousands of files day in and day out and even in this case only SSD disks are affected. Considering that SSD disk operations are sometimes several orders of magnitude faster than those for spinning disks this performance loss is still nothing to worry about.
I guess they won't be affected unless your application reads and writes data from/to the disk one byte at a time. People have already run network tests and the KPTI patch has a minimum performance loss.
I wonder if large corporations have any notion of conscience because the Intel ME fiasco is just too fresh in our memory to make such outrageous claims.
I like how they've weaseled out of the whole fiasco (why didn't /. post a link to the original press release?):
"Contrary to some reports, any performance impacts are workload-dependent, and, for the average computer user, should not be significant and will be mitigated over time".
I'm not sure I can read between the lines properly but I guess new revisions of Coffee Lake/Kaby Lake/SkyLake(X) CPUs are coming and they will contain a hardware fix (though it still seems highly unlikely considering how difficult it's to deploy a new hardware design - however unlike other fabless companies, like AMD/NVIDIA/ARM/etc Intel has everything under control). After all they've known about this issue for almost half a year.
Meanwhile as for consumer workloads they are correct. Two German websites have already tested a Windows build with a fix and found very little performance losses.
Phoronix has also run a number of tests on Linux and found out that only few (mostly artificial) tasks are seriously affected.
Intel home users may sleep well. As for enterprise customers no one has run virtualization tests yet though - that's what truly important for large deployments (clouds).
I'm inclined to believe that Edge's advantage comes from its ability to utilize [GPU] hardware acceleration better and not from cheating on Microsoft's part.
With 99.99% certainty unless the Mach kernel does something no other OS does in order to secure kernel memory pages.
I'm curious how much Cannon Lake and Ice Lake CPU architectures are going to be delayed. Since Cannon Lake is basically SkyLake on a 10nm node, Intel cannot release it with such a glaring hole which causes such a significant performance loss.
I've been running a Sandy Bridge CPU for seven years now, and now I'm really looking forward to the second gen Zen CPUs. Viva, competition. I'm really glad AMD is still around.
Results varied. Some workflows experienced a very significant performance loss however, e.g. Firefox became twice as slow, WinRAR four times as slow.
Have you just hit infamous bug 12309? It's ostensibly fixed however people keep reproducing it (just google for heavy I/O operations slow down my PC).
Some PostgreSQL results have just been released: up to 23% performance loss. This is indeed huge.
The developers behind the GRSecurity project measured up to 63% performance loss. If most common tasks are equally affected, Intel is sure fucked. Home users might not need to bother, but large cloud providers might be seriously affected.
Meanwhile the Linux kernel has received the largest incremental minor patch in its history (229KiB) - perhaps kernel 4.14.11 already contains all the required fixes.
I have a sneaking suspicion Intel shares will fall through the floor in the next few weeks because Intel CPUs might have suddenly become quite slower than their AMD Zen based counterparts.
I wonder if I sell my entire body for parts, will I be able to afford this TV set?
What's even funnier is that I posted a link to this interview in the original post which ran two days ago and it garnered zero response.
On Youtube.
The main takeaways:
He's done that many times.
He enjoys "evacuating" (swatting) people.
He was paid for this particular SWAT call.
He understands he's indirectly responsible for the killing and he's ready to serve jail time (just not a life sentence) if he gets caught (he's already been apprehended).
Your fears are totally warranted as the new UI looks like modern shit we are already forced to consume in other OS'es like Windows 10.
Hopefully the new Thunderbird will be themeable but I wouldn't hold my breath considering that theming was essentially killed in Firefox (we can only apply a background image to its bars - that's it).
I haven't watched a lot of them in 2017 but my top picks are "Shot Caller" and "Wind River".
Of course, the answer will be "no".