The best way out for users seems to be to look for an alternative to Intel, there's not point trying to get water out of a stone and their attitude stinks, not to mention the other negatives like IME. AMD seem better over all but they have a management engine of their own and even ARM does to some extent.
The most likely outcome I see is a rebate/coupon towards the purchase of any system containing a new Intel CPU from any vendor where the dollar value of the rebate is tied to the age/sku of the old CPU, with no or soft requirements to return the old CPU
That rebate is extremely unlikely to cover more than the value of the CPU, what about the secondary cost of replacing the rest of the computer it was attached to. If it uses a different socket, or is soldered directly or more likely isn't even compatible anyway, then it has been rendered worthless. I don't buy a new computer every year, nor do I want to: consumer looses, Intel wins.
You forgot to bombard the tray with a tachyon pulse... just plug your headphones into the line-out jack, side->load your nanocode into the IMU and use the 3rd master jumper configuration (the stripey one with a reindeer). Don't forget to butter afterwards not before.
Surely they can just remodulate the the dampening field to allow for higher dimensional transformations in the instruction capacitor in order to invoke the HCF instruction and BURN IT TO HELL!!!11!1
I don't see how else they could "expect to have patched 90 percent of its processors", Intel doesn't control all kernels ever. It's also what everyone else is talking about in response to this announcement. A microcode patch from intel was expected... what wasn't known is how much could be fixed in microcode, and as it turns out - not all of it, that's why we still have the OS specific kernel patches.
I meant RAM. The CPU usually has a microcode ROM version that never changes, this gets loaded into the on die microcode RAM on boot... then potentially the BIOS/UEFI might upload a newer version (overwriting the microcode RAM)... after that finally the OS most likely has the latest microcode version that it wants to load directly. I don't know if there is a process that checks the version to prevent old ones overwriting new ones but it looks like the OS has the final say anyway.
Intels updates also slow down AMD chips that don't have the bug as well. And AMD had to come out with there own update to back off the big slow down fix that Intel patch
I think your mixing things up... this announcement is for microcode update, microcode is specific to a CPU, you can't apply an intel's CPU microcode to an AMD, they are implementation specific and cryptographically signed.
The AMD slowdowns are from kernel patches that do not discriminate between Intel and AMD, those patches are not from Intel they are efforts of kernel developers of the various major OS.
No... I'll just get a different CPU next time. Especially since they don't seem to be bothering with microcode patches for 5yr old CPUs, so Intel CPUs are a bad investment it would seem.
They might be "in" the BIOS in the most temporary sense as part of a firmware update but they are for the CPU which once verified will copy it into the CPU's ROM.
The confusion comes from the fact that microcode updates sometimes hitch a ride on a firmware update for the BIOS/UEFI that in turn passes the microcode update to the CPU. Alternatively the OS might get there first and obviate the BIOS patch (Macs are more likely to receive microcode via firmware update and PCs are more likely to receive it via an OS update long before the various hardware vendors get around to issuing a BIOS/UEFI update)
I don't care about the "free market" or "net energy exporter" arguments, the important thing is that Norway has contributed substantially to electric car sales... This in turn will help accelerate technological improvements and drive cost down through mass production. That is the key catalyst that is needed to make turn a "viable technology" into a widely available and affordable technology.
...than some sort of idealized utopia of unicorns and rainbows where we all love each other
It's not necessary or even preferable to for us to "all love each other" in order to progress and be civilised. Painting whatever the current system is as imperfect because it's not reaching something both undesirable and unattainable is the best example of a straw man i've ever seen (what a boring world it would be if we all got along perfectly).
Also, heat? 1-2 degrees of extra heat is not going to cause cancer. Counterexample - Humans wear clothes, which increases body temperature. Year wearing clothes does not increase cancer rates by any noticeable amount.
You are disregarding localisation. There are many ways to apply heat, in your ill fitting analogy you are drawing upon the very tangible methods such as convection and conduction as mechanisms of transport into the body, localised high temperature spots don't naturally occur in the mediums that facilitate those methods and even if they did they would dissipate before deeply penetrating the body.
Heat emerging from interaction with penetrating radiated energy is a different kind of beast, however you should be able to use a microwave oven as a decent starting point for your imagination. Also keep in mind that RF radiation has many subtleties, it's not as simple as most people imagine, it doesn't simply penetrate matter in the way that light penetrates a vacuum, it interacts with the matter is passes through in complex ways - ask a decent RF engineer and they will describe the intricate and unpredictable ways a signal can propagate about structures and the challenges it posses in telecommunications. Any kind of focusing effect could cause a localised heating effect, maybe only an average of 1-2 degrees over a cubic millimetre, but if localised enough within that millimetre it could be enough to unravel some DNA.
And if the temperature increase from a cell phone causes cancer, then god forbid what holding hands or carrying a baby must do to people. Why, they'd be nothing but walking tumors within a year!
I know you are being facetious but you surely understand that cause and effect of cancer are often separated far in time... no one knew the dangers of asbestos until is had been around for long enough. Carcinogens are many and their toxicity notoriously difficult to quantify given the latent nature of cancer. My point is that from a scientific point of view you are being quite arrogant and dismissive (we don't know everything about the interaction between biological matter and low intensity microwave radiation), however your argument about the legislation being a bit preemptive is more valid.
Nothing is a perfect isotropic radiator... what is you point? inverse square law still applies unless cell phones have suddenly started using quantum tunnelling instead of old fashioned RF. It is valid to the discussion because of how it applies to the signal amplitude falloff and therefore proximity makes a big difference, it not being a perfectly isotropic is irrelevant.
Cut off your nose to spite your face, that's the Oracle gameplan 101. They are mad at Google so they will try to destroy android, the only software keeping Java relevant.
Smart as always.
Regardless of the truth of your Java statement (I'm not a Java fan FYI), this is just not how Oracle operates, and no i'm not an Orcale expert either - but it's clear from their history that they don't care about long term investments, they care about buying up and cashing out all IP possible, often through litigation... they are run by lawyers and salesmen alone without any concern for more than their bottom line.
The quotes allow for de-escalation synonym transposition that helps to stabilize the reality distortion field that protects the mac psyche... without it Apple would surely implode.
"distributed version control system" does not define git, that's more of a side effect. That's the problem with people who don't get git, evident in the countless comparisons when you google "the difference between git and mercurial" (two good distributed SCMs), they are full of misinformation and comparisons of things that work on top of git like git client UIs and git webserver interfaces.
The XKCD is probably the most accurate description: "it's a beautiful simple use of graph theory which is extremely flexible... and I have no idea how it works" It's accurate, acknowledges git's beauty and power and the unfortunate truth that most people don't really understand it and view it through the sometimes questionably design porcelain commands.
The grain of truth however in any of these shitty comparisons around the web, is how some git porcelain commands are confusing because they indeed provide many functions in the same utility which is ironic since git is considered very unix like in how it is built upon a collection of plumbing tools that mutate a graph of objects and merkel trees... If git could be improved for the 90% of people who don't care or "get" git, it's these handful of commonly used porcelain commands like checkout, they need to be more modular like mercurial, additionally they need to not mislead less knowledgeable users about what's really happening (some porcelain commands look like they emulate SVN commands but they really don't, they just look that way on the surface)
Git is always confusing when coming from most other SCM because it's almost nothing like most other SCM. It's biggest strength it's it's biggest hurdle, when you learn it from the outside in like most people (touching only the common porcelain commands) it's very easy to build up misconceptions that you can get away with but will confuse the fuck out of you as you try to expand your knowledge. To be fair to the git book beginner chapters and other tutorials they do attempt to reveal internals along the way but I don't think it focuses enough on them. To make matters worse the porcelain commands often look and sound very similar to other SCMs that work nothing like a content addressed file system.
If you do a deep dive and are lucky enough to have time to spend on git internals then honestly you can just skim read the commands and they fall into place because you will have a good understanding of how they are all just arbitrary high level ways of manipulating a fairly straightforward data structure. Perhaps this is why git books and tutorials really should bother emphasising and explaining some level of internals more upfront. I think as a starter thinking about commits as objects alone (without going into tree, blob and tag objects) along with branches as commit references is enough to explain how almost all the porcelain commands operate on a graph.
You are comparing a toy that was designed or manufactured carelessly to youtube videos that were designed to spread perversion and corrupt our children. This is a problem.
... yeah you are right, it's not a sound analogy, the difference is that the videos passing through the filter are not broken or malicious, they are just intended for a different audience, and to remove them would be nothing less than baby proofing the world.
Boohoo, a kid unfriendly southpark-esc satire slipped through an AI filter: The end of the internet is not nigh, this is a product issue: Google's kiddy product. Author: try applying your logic to tangible goods: a kiddy toy was found to have sharp edges - something is fundamentally wrong with the manufacturing industry.
Slashdot Mirror
Yo Brian, It takes courage to put bugs in your bugs.
Clearly putting a CPU in their CPU wasn't enough.
...Yes i'm replying to my own comment, it's not weird, i'll be here all week.
The Intel exec said users shouldn't feel discouraged by these snags and continue to install updates from OS makers and OEMs.
Yo Brian, It takes courage to put bugs in your bugs.
The best way out for users seems to be to look for an alternative to Intel, there's not point trying to get water out of a stone and their attitude stinks, not to mention the other negatives like IME. AMD seem better over all but they have a management engine of their own and even ARM does to some extent.
The most likely outcome I see is a rebate/coupon towards the purchase of any system containing a new Intel CPU from any vendor where the dollar value of the rebate is tied to the age/sku of the old CPU, with no or soft requirements to return the old CPU
That rebate is extremely unlikely to cover more than the value of the CPU, what about the secondary cost of replacing the rest of the computer it was attached to. If it uses a different socket, or is soldered directly or more likely isn't even compatible anyway, then it has been rendered worthless. I don't buy a new computer every year, nor do I want to: consumer looses, Intel wins.
Tried that, it burnt my toast. Can't have that.
You forgot to bombard the tray with a tachyon pulse... just plug your headphones into the line-out jack, side->load your nanocode into the IMU and use the 3rd master jumper configuration (the stripey one with a reindeer). Don't forget to butter afterwards not before.
Surely they can just remodulate the the dampening field to allow for higher dimensional transformations in the instruction capacitor in order to invoke the HCF instruction and BURN IT TO HELL!!!11!1
I don't see how else they could "expect to have patched 90 percent of its processors", Intel doesn't control all kernels ever. It's also what everyone else is talking about in response to this announcement. A microcode patch from intel was expected... what wasn't known is how much could be fixed in microcode, and as it turns out - not all of it, that's why we still have the OS specific kernel patches.
I meant RAM. The CPU usually has a microcode ROM version that never changes, this gets loaded into the on die microcode RAM on boot... then potentially the BIOS/UEFI might upload a newer version (overwriting the microcode RAM)... after that finally the OS most likely has the latest microcode version that it wants to load directly. I don't know if there is a process that checks the version to prevent old ones overwriting new ones but it looks like the OS has the final say anyway.
Intels updates also slow down AMD chips that don't have the bug as well. And AMD had to come out with there own update to back off the big slow down fix that Intel patch
I think your mixing things up... this announcement is for microcode update, microcode is specific to a CPU, you can't apply an intel's CPU microcode to an AMD, they are implementation specific and cryptographically signed.
The AMD slowdowns are from kernel patches that do not discriminate between Intel and AMD, those patches are not from Intel they are efforts of kernel developers of the various major OS.
but only going back to Haswell is just going to encourage a lot of people to buy new CPUs. From AMD.
Indeed, that is my personal conclusion, unless they go back further with the microcode, no more Intel for me.
No... I'll just get a different CPU next time. Especially since they don't seem to be bothering with microcode patches for 5yr old CPUs, so Intel CPUs are a bad investment it would seem.
CPU microcode updates are in bios as well.
They might be "in" the BIOS in the most temporary sense as part of a firmware update but they are for the CPU which once verified will copy it into the CPU's ROM.
The confusion comes from the fact that microcode updates sometimes hitch a ride on a firmware update for the BIOS/UEFI that in turn passes the microcode update to the CPU. Alternatively the OS might get there first and obviate the BIOS patch (Macs are more likely to receive microcode via firmware update and PCs are more likely to receive it via an OS update long before the various hardware vendors get around to issuing a BIOS/UEFI update)
I don't care about the "free market" or "net energy exporter" arguments, the important thing is that Norway has contributed substantially to electric car sales... This in turn will help accelerate technological improvements and drive cost down through mass production. That is the key catalyst that is needed to make turn a "viable technology" into a widely available and affordable technology.
...than some sort of idealized utopia of unicorns and rainbows where we all love each other
It's not necessary or even preferable to for us to "all love each other" in order to progress and be civilised. Painting whatever the current system is as imperfect because it's not reaching something both undesirable and unattainable is the best example of a straw man i've ever seen (what a boring world it would be if we all got along perfectly).
it applies enough... the difference between keeping it in your pocket and in a bag is likely large enough that inverse square law applies.
Also, heat? 1-2 degrees of extra heat is not going to cause cancer. Counterexample - Humans wear clothes, which increases body temperature. Year wearing clothes does not increase cancer rates by any noticeable amount.
You are disregarding localisation. There are many ways to apply heat, in your ill fitting analogy you are drawing upon the very tangible methods such as convection and conduction as mechanisms of transport into the body, localised high temperature spots don't naturally occur in the mediums that facilitate those methods and even if they did they would dissipate before deeply penetrating the body.
Heat emerging from interaction with penetrating radiated energy is a different kind of beast, however you should be able to use a microwave oven as a decent starting point for your imagination. Also keep in mind that RF radiation has many subtleties, it's not as simple as most people imagine, it doesn't simply penetrate matter in the way that light penetrates a vacuum, it interacts with the matter is passes through in complex ways - ask a decent RF engineer and they will describe the intricate and unpredictable ways a signal can propagate about structures and the challenges it posses in telecommunications. Any kind of focusing effect could cause a localised heating effect, maybe only an average of 1-2 degrees over a cubic millimetre, but if localised enough within that millimetre it could be enough to unravel some DNA.
And if the temperature increase from a cell phone causes cancer, then god forbid what holding hands or carrying a baby must do to people. Why, they'd be nothing but walking tumors within a year!
I know you are being facetious but you surely understand that cause and effect of cancer are often separated far in time... no one knew the dangers of asbestos until is had been around for long enough. Carcinogens are many and their toxicity notoriously difficult to quantify given the latent nature of cancer. My point is that from a scientific point of view you are being quite arrogant and dismissive (we don't know everything about the interaction between biological matter and low intensity microwave radiation), however your argument about the legislation being a bit preemptive is more valid.
Nothing is a perfect isotropic radiator... what is you point? inverse square law still applies unless cell phones have suddenly started using quantum tunnelling instead of old fashioned RF. It is valid to the discussion because of how it applies to the signal amplitude falloff and therefore proximity makes a big difference, it not being a perfectly isotropic is irrelevant.
Cut off your nose to spite your face, that's the Oracle gameplan 101. They are mad at Google so they will try to destroy android, the only software keeping Java relevant.
Smart as always.
Regardless of the truth of your Java statement (I'm not a Java fan FYI), this is just not how Oracle operates, and no i'm not an Orcale expert either - but it's clear from their history that they don't care about long term investments, they care about buying up and cashing out all IP possible, often through litigation... they are run by lawyers and salesmen alone without any concern for more than their bottom line.
Why the quotes around exploit?
The quotes allow for de-escalation synonym transposition that helps to stabilize the reality distortion field that protects the mac psyche... without it Apple would surely implode.
"distributed version control system" does not define git, that's more of a side effect. That's the problem with people who don't get git, evident in the countless comparisons when you google "the difference between git and mercurial" (two good distributed SCMs), they are full of misinformation and comparisons of things that work on top of git like git client UIs and git webserver interfaces.
The XKCD is probably the most accurate description: "it's a beautiful simple use of graph theory which is extremely flexible... and I have no idea how it works" It's accurate, acknowledges git's beauty and power and the unfortunate truth that most people don't really understand it and view it through the sometimes questionably design porcelain commands.
The grain of truth however in any of these shitty comparisons around the web, is how some git porcelain commands are confusing because they indeed provide many functions in the same utility which is ironic since git is considered very unix like in how it is built upon a collection of plumbing tools that mutate a graph of objects and merkel trees... If git could be improved for the 90% of people who don't care or "get" git, it's these handful of commonly used porcelain commands like checkout, they need to be more modular like mercurial, additionally they need to not mislead less knowledgeable users about what's really happening (some porcelain commands look like they emulate SVN commands but they really don't, they just look that way on the surface)
Git is always confusing when coming from most other SCM because it's almost nothing like most other SCM. It's biggest strength it's it's biggest hurdle, when you learn it from the outside in like most people (touching only the common porcelain commands) it's very easy to build up misconceptions that you can get away with but will confuse the fuck out of you as you try to expand your knowledge. To be fair to the git book beginner chapters and other tutorials they do attempt to reveal internals along the way but I don't think it focuses enough on them. To make matters worse the porcelain commands often look and sound very similar to other SCMs that work nothing like a content addressed file system.
If you do a deep dive and are lucky enough to have time to spend on git internals then honestly you can just skim read the commands and they fall into place because you will have a good understanding of how they are all just arbitrary high level ways of manipulating a fairly straightforward data structure. Perhaps this is why git books and tutorials really should bother emphasising and explaining some level of internals more upfront. I think as a starter thinking about commits as objects alone (without going into tree, blob and tag objects) along with branches as commit references is enough to explain how almost all the porcelain commands operate on a graph.
You are comparing a toy that was designed or manufactured carelessly to youtube videos that were designed to spread perversion and corrupt our children. This is a problem.
... yeah you are right, it's not a sound analogy, the difference is that the videos passing through the filter are not broken or malicious, they are just intended for a different audience, and to remove them would be nothing less than baby proofing the world.
They can't search for "install iOS 10" to revert... because they can't type "i"
HaahAHAHahhahahaha hAHAHahahaHhaHAhahahaaaaa haaa haaaa.... haaaaaaaaaa.haahahahahaa. Good one Microsoft.
Boohoo, a kid unfriendly southpark-esc satire slipped through an AI filter: The end of the internet is not nigh, this is a product issue: Google's kiddy product. Author: try applying your logic to tangible goods: a kiddy toy was found to have sharp edges - something is fundamentally wrong with the manufacturing industry.