My wife is a good example of the main iPhone market demographic: she's not technically savvy, just wants it "to work," and when they push changes, she doesn't really notice and rolls with it. As long as iMessage and FaceTime work, she's happy.
She has an iPhone 7. I recently changed the battery for her, and told her if she wanted to look at a new phone, we could. She was sort of excited. Until we got to the store. They pulled out the iPhone X line, and told her the prices, starting at $1,000 USD (for the 64GB version of the X S). She instantly said "no thank you" and we left the store. She took zero time to look at the different screen resolution, the better camera, the faster processor, etc. She just didn't care. It was way too expensive. And our joint income would allow us to afford this without even noticing, but it was the principle of the matter.
This ban is something that has been happening all over the world in some shape or form. Personally, I have little problem with it. I'm actually happy to see when a restaurant or coffee shop has utensils that are biodegradable. It's a great move.
What I don't like, from the end of this article, is the other part of the EU proposal. Why should the manufacturers be responsible for preventing people from being jackasses and throwing their garbage wherever they please? There are so many analogies to make here, it's not worth it.
People ultimately need to be held responsible for proper disposal and/or recycling of materials and consumables they are consuming. The manufacturer in this case isn't building in some weird feature making it difficult to throw the stirring straw in a garbage can. People just need to start being more responsible and not thinking that someone else will clean up after them.
The issue isn’t they didn’t provide this or that, the core issue is they were addressing an isolated issue with some phones shutting down unexpectedly due to current draw on older batteries. It wasn’t a fully-widespread issue. Only on a subset of phones out there. But the solution was to apply the throttling everywhere, under the radar. That is the issue.
If they were more forthcoming, they could have positioned it as “through additional research based on isolated customer reports, we have found that in certain cases, aging batteries can cause a phone to unexpectedly shut down under heavy use. Therefore, we are implementing changes to mitigate this potential issue by throttling performance under these heavy-use scenarios. We are also introducing a toggle for users to opt-out of this throttling behavior, if they choose to do so. We apologize for any convenience this may be causing.”
Be up front about the issue, say why you’re making this blanket change to correct a somewhat isolated incident, and let people choose if they want performance or a potential shutdown of their phone. Ramming the behavior into the device without opt-in or control, or even disclosure (until they got caught) only reminds everyone that you only rent your devices, you don’t own them.
Unfortunately, the people who are too blinded by their pure hatred of one extreme or the other cannot see past that hatred and see the reality of what is happening. Or they're just not willing to admit a politician is actually fulfilling campaign promises, for better or worse.
Yet another prime example of why alien civilizations won't contact us openly: How can a truly civilized race possibly take us as anything other than animals when we still do things like this? Our so-called "civilization" is just as thin a patina over the animal underneath as our neo-cortex is over the rest of our brains. It's positively heartbreaking to read of things like this in this day and age when I know that the human race, at it's best, is in such stark contrast with such senseless ignorance and brutality.
I don't disagree with your overall premise, but what says that an alien civilization with technology to travel inter-planet has to be a truly civilized race?
Sorry, but this isn't significant. And to be honest, it sounds like it should be in the noise. Flash memory is flash memory. The cell can swell based on many environmental factors (air pressure changes, humidity, temperature, etc.), and TFA clearly mentions heat as a possible factor. The fact a downloaded piece of data measured at all could be the cells were heated as the gates were being used to store the data. Who knows. A billionth of a billionth of a gram for 4GB of data just sounds too tiny to be remotely significant, let alone noteworthy outside of an extremely controlled environment.
I'd like to see more data on the experiment itself, to see if the measurements were all taken in a very controlled environment or not. TFA is really lacking any details that would intrigue people who cared.
The issue today though isn't in-house vs. colocated, it's cost. Most of these companies don't have the cash to build proper infrastructure to house their services locally. The cloud services from various companies, like Amazon, take care of the physical maintenance and cooling and power, etc.
Even if your local datacenter housed mission-critical data, I'm sure it's possible to come up with 100 scenarios where you could lose all connectivity to your locally-housed infrastructure (power company accidentally digs up your comm lines, etc.).
The cloud isn't perfect, but neither is in-house colocation. It depends on how much money you want to spend for the control. Even with the control, you can't plan for the worst and still remain cost-effective. This is just a crappy situation that is amplified given how many people rely on the services.
Don't forget about the NVidia Ion platforms. They also use a "just-enough" CPU in Intel's Atom, with higher end NVidia GPUs to run nicely integrated HD set-top boxes. Nice little platforms for MythTV frontends.
I don't play games on my laptop, but I do run compiz-fusion with many of the features enabled. It's very eye-candy-heavy, and my integrated Intel graphics chip keeps up just fine. My CPUs don't bear much load at all. I don't think things are as grossly out of proportion as you make them out to be. 5 years ago, yes. Today, not so much.
Another big portion is companies like Novell contract themselves to other companies to do their kernel development for them. AMD, for example, pays Novell to do their kernel work for them. This isn't an uncommon practice, since RedHat also gets money from other companies to do their development work in the kernel. But when it comes down to it, the actual "originator" of the code or concept may not be Novell or RedHat, but they're the email address getting merged on the Signed-off-by: lines, which isn't a big deal.
I don't see this as anything evil or underhanded, being a network stack hacker myself. The kernel maintainers and core contributers are far from stupid and gullible, and will *not* accept anything if they see proprietary undertones. I'm also sure they're putting a bit more scrutiny into reviewing patches from Novell just because. But the bottom line is more people are working on the kernel, trying to make it better, which is the end-goal. It really, in my mind, doesn't matter who is doing it, just as long as it's getting done and done well.
Just because it hasn't happened doesn't mean it isn't a possibility of happening. If the TSA waited to have something bad happen everytime before they added it to the list of things to inspect, we'd have many more incidents. Granted the shoe inspection is because of the infamous attempted shoe bomber, but that reality check for them prompted other checks.
I get annoyed by the security checks, but if there is a remote possibility that those checks might catch someone really intending on causing something bad to happen, I'm willing to deal with it.
And I'm sure there were a large number of passengers that have the same "techy" level that the TSA agents did, let's not be so hard on those people. I'd rather the TSA agent err on the side of caution than not, and letting something flagrant through screening. Odd that this made the news, when we (society) seem to love pointing out the failures of the TSA of *not* stopping bad things.
One of the things that makes a big impact on performance, on any platform, is the type and speed of memory used. Looking at your list of platforms above, I see an HP Workstation used with the Opteron. Not having one in front of me to verify, but reading on HP's website what chipset and memory is available, you could get a very distinct increase in performance simply due to lower memory latency through the chipset and memory type.
What chipset(s) and memory were used in the Mac's? Were they on-par with a workstation-level machine from HP?
The G5 doesn't surprised me. The underlying architecture, a consumer version of the Power5, is a damn good architecture. But it needs code compiled to use what makes it fast, which is the altivec stuff. I remember watching a G4 right after it released smoke anything on the market with RC5 number crunching *only* if you ran the RC5 passes with altivec enabled. If you ran it with a standard optimization, it got crushed by the Tualatin P3's we had in the labs.
Bottom line is anyone can post benchmark results, but when they don't have a level playing field for their hardware, it's comparing apples to oranges. If the code has any specific code optimizations for any of the processor's respective strengths, then it's apples to oranges. If you post numbers like this, either be prepared to lay out what you specifically used (hardware, software), or be prepared to have long discussions asking for these things. This is why the hardware magazines on the net always use the same application with very well-published hardware setups, so they don't get questions and scrutiny like we have here. Apples to apples is what people like to see. Other data is interesting, but is subject to questions.
Care to publish your numbers that debunk all the other hardware sites that are typically AMD-biased anyways?
And pointing out that it isn't fair to compare because a Core2 duo already executes the full SSE instruction in one pass vs. the 2 clocks for a curret AMD64 is the same as saying it's not fair to compare the on-die memory controller on AMD's vs. Intel's FSB. But people didn't seem to care when the numbers went in AMD's favor.
I'd really be interested in seeing your numbers, your programs, and what compiler options you passed when building on each platform (as well as type of memory, mobo chipset, etc., in each machine).
Broadly waving your hand and stating that it's easy to come up with a new design for the new model is rather naive. While the physics may have not changed, be rest assured the operating conditions, or even the requirements have. Apply this logic to the AK-47. If Kalashnikov just "used the previous model" as a basis of development, who knows what we would have gotten. Instead, he looked at what existed to say what wasn't needed anymore (warfare had changed from long-range firing to more dynamic, medium-to-short-range fighting), and took 4 years to design, build, and have the AK-47 adopted as a main-stream weapon. And 60 years later, it's still in use, with the same design as it had back then.
The US military had a similar experience with the M-16. Very reliable gun, it took a long time with *tons* of testing by the military to adopt it. If you're interested, read this: http://en.wikipedia.org/wiki/M16_rifle.
Innovation of a next-generation thing may seem simple, and can easily be brushed off as trivial. But until you understand what really is going on, and why certain things take so long to really perfect, don't push people's efforts and attention to detail to the side.
Being someone who's survived both a nasty car crash and a moderate motorcycle accident, I have to say I agree with both the laws for seat belts and helmets, respectively. I know that people think seat belts are a pain in the ass to wear, and helmets aren't "cool" when pimping your ride, but as an anonymous motorist that has the unfortunate accident involving one of the former, having a bit of safety in those vehicles might prevent someone from having an accidental death on their conscience. If you happened to drive through an intersection with a green light, but someone not paying attention drove through, not wearing a seat belt, and was launched from the vehicle and killed after you hit him/her, I really don't care who's fault it was, etc., or how much your insurance costs; the fact is that person will have to live with the fact they were responsible - not at fault - for someone's death. That is worse than any insurance hike, etc. It's not just you on the road being "inconvieneced" by a helmet or seat belt law; it's for the peace of mind of everyone else on the damn road you might kill or be killed by because of some unfortunate accident.
Now, if someone is detached enough to be so involved with crossing a street and not seeing a car or bus, ask a motorcyclist how many times they've been cut off by a car that "didn't see them." It goes both ways.
I fortunately don't speak from experience, but I relay from friends of mine that unfortunately have experience in this department.
The patent surrounds the method of storing data on an device to persist indefinately. I want to know any hardware vendor today that makes some form of silicon or any other storage medium that lasts indefinately, or one that has announced plans to make such a device. Microsoft has some really interesting things coming out of their research labs, but this one makes me scratch my head, since they are not a hardware company, and no hardware company has anything remotely close to handling this research. While it's very interesting to be thinking of these things, I don't see why this is a big deal as compared to any other research project any other technology company may be working on.
Honestly, this is making headlines because whenever Microsoft files for obscure patents that their rather talented architects and strategic planners can forsee, they are challenged on the basis of validity for their patent. If some startup somewhere was doing this research, it would have never made/. Compare this to all research being done in quantum computing arenas, where some rather radical advances and theories are being pursued, way more radical than this. Do you read about them here? Not usually.
Then again, the ol' rock, chisel, and hammer seemed to hold information for a damn long time...
If someone is concerned with traffic shaping, they probably have some clue as to how networks and network flows work. Given that, if they can't figure out how to use the interface to the various QoS solutions, then 1) they're a manager pissed off their web traffic is too slow, or 2) they just need to spend some time with either interface to figure it out.
I have used tc in Linux very heavily, and it can get complicated when specifying filters. I wouldn't expect someone with no idea of what bandwidth allocation is to use it effectively.
Moore's Law doesn't say the speed of a processor will double every 18 months, it states the density of an integrated circuit (i.e. number of transistors) will double every 18 months.
A few years ago, Intel changed the title of all the software engineers working for the software automation of the fabs to automation engineers. Interesting that the management did that when there was a mandatory market adjustment (increase) in pay for software engineers for that review cycle. They changed the titles right before the cutoff date, and screwed a few thousand engineers out of a mandatory raise.
Luckily, I got out of there before they did this. Shitty though? Yes.
Collateral damage is imminent in war. The coalition forces issued many warnings to the civilians of Fallujah to leave before we hit it full-force. If people didn't leave, then they fall under the collateral damage figures of war. I'm not saying this to condone any civilian losing their life in the cross-fire, but shit happens in war.
As far as I can recall, Saddam ordering the deaths of civilians was *not* in a time of war. Therefore it's not collateral damage, it's murder.
Just speculation, but the fact the layout of the motherboard to prevent clutter is more significant than you'd think. In systems with bleeding edge components, you will have components that will still be pulling a generous amount of power. If you have cluttered cables around main airways across the motherboard, you don't remove heat as fast as a well-designed and channeled system. If it's really bad, then you can overheat the machine and have components shut themselves down, or clock themselves down.
Something as little as component layout can make a huge impact.
Slashdot Mirror
My wife is a good example of the main iPhone market demographic: she's not technically savvy, just wants it "to work," and when they push changes, she doesn't really notice and rolls with it. As long as iMessage and FaceTime work, she's happy.
She has an iPhone 7. I recently changed the battery for her, and told her if she wanted to look at a new phone, we could. She was sort of excited. Until we got to the store. They pulled out the iPhone X line, and told her the prices, starting at $1,000 USD (for the 64GB version of the X S). She instantly said "no thank you" and we left the store. She took zero time to look at the different screen resolution, the better camera, the faster processor, etc. She just didn't care. It was way too expensive. And our joint income would allow us to afford this without even noticing, but it was the principle of the matter.
She may be converting to a Pixel in the future...
This ban is something that has been happening all over the world in some shape or form. Personally, I have little problem with it. I'm actually happy to see when a restaurant or coffee shop has utensils that are biodegradable. It's a great move.
What I don't like, from the end of this article, is the other part of the EU proposal. Why should the manufacturers be responsible for preventing people from being jackasses and throwing their garbage wherever they please? There are so many analogies to make here, it's not worth it.
People ultimately need to be held responsible for proper disposal and/or recycling of materials and consumables they are consuming. The manufacturer in this case isn't building in some weird feature making it difficult to throw the stirring straw in a garbage can. People just need to start being more responsible and not thinking that someone else will clean up after them.
The lists are mostly hosted on vger.kernel.org. LKML is just fine. LKML.org is just a web archive.
The issue isn’t they didn’t provide this or that, the core issue is they were addressing an isolated issue with some phones shutting down unexpectedly due to current draw on older batteries. It wasn’t a fully-widespread issue. Only on a subset of phones out there. But the solution was to apply the throttling everywhere, under the radar. That is the issue.
If they were more forthcoming, they could have positioned it as “through additional research based on isolated customer reports, we have found that in certain cases, aging batteries can cause a phone to unexpectedly shut down under heavy use. Therefore, we are implementing changes to mitigate this potential issue by throttling performance under these heavy-use scenarios. We are also introducing a toggle for users to opt-out of this throttling behavior, if they choose to do so. We apologize for any convenience this may be causing.”
Be up front about the issue, say why you’re making this blanket change to correct a somewhat isolated incident, and let people choose if they want performance or a potential shutdown of their phone. Ramming the behavior into the device without opt-in or control, or even disclosure (until they got caught) only reminds everyone that you only rent your devices, you don’t own them.
Unfortunately, the people who are too blinded by their pure hatred of one extreme or the other cannot see past that hatred and see the reality of what is happening. Or they're just not willing to admit a politician is actually fulfilling campaign promises, for better or worse.
Ah Sri, you really do always have a smile on your face. :-)
Yet another prime example of why alien civilizations won't contact us openly: How can a truly civilized race possibly take us as anything other than animals when we still do things like this? Our so-called "civilization" is just as thin a patina over the animal underneath as our neo-cortex is over the rest of our brains. It's positively heartbreaking to read of things like this in this day and age when I know that the human race, at it's best, is in such stark contrast with such senseless ignorance and brutality.
I don't disagree with your overall premise, but what says that an alien civilization with technology to travel inter-planet has to be a truly civilized race?
It's only mandatory on ARM devices that wish to be Windows Logo certified.
Maybe the year of Linux on the desktop is coming after all. Slowly, but eventually.
It's been here for awhile. It's called Android.
Sorry, but this isn't significant. And to be honest, it sounds like it should be in the noise. Flash memory is flash memory. The cell can swell based on many environmental factors (air pressure changes, humidity, temperature, etc.), and TFA clearly mentions heat as a possible factor. The fact a downloaded piece of data measured at all could be the cells were heated as the gates were being used to store the data. Who knows. A billionth of a billionth of a gram for 4GB of data just sounds too tiny to be remotely significant, let alone noteworthy outside of an extremely controlled environment.
I'd like to see more data on the experiment itself, to see if the measurements were all taken in a very controlled environment or not. TFA is really lacking any details that would intrigue people who cared.
The issue today though isn't in-house vs. colocated, it's cost. Most of these companies don't have the cash to build proper infrastructure to house their services locally. The cloud services from various companies, like Amazon, take care of the physical maintenance and cooling and power, etc.
Even if your local datacenter housed mission-critical data, I'm sure it's possible to come up with 100 scenarios where you could lose all connectivity to your locally-housed infrastructure (power company accidentally digs up your comm lines, etc.).
The cloud isn't perfect, but neither is in-house colocation. It depends on how much money you want to spend for the control. Even with the control, you can't plan for the worst and still remain cost-effective. This is just a crappy situation that is amplified given how many people rely on the services.
Don't forget about the NVidia Ion platforms. They also use a "just-enough" CPU in Intel's Atom, with higher end NVidia GPUs to run nicely integrated HD set-top boxes. Nice little platforms for MythTV frontends.
I don't play games on my laptop, but I do run compiz-fusion with many of the features enabled. It's very eye-candy-heavy, and my integrated Intel graphics chip keeps up just fine. My CPUs don't bear much load at all. I don't think things are as grossly out of proportion as you make them out to be. 5 years ago, yes. Today, not so much.
Another big portion is companies like Novell contract themselves to other companies to do their kernel development for them. AMD, for example, pays Novell to do their kernel work for them. This isn't an uncommon practice, since RedHat also gets money from other companies to do their development work in the kernel. But when it comes down to it, the actual "originator" of the code or concept may not be Novell or RedHat, but they're the email address getting merged on the Signed-off-by: lines, which isn't a big deal.
I don't see this as anything evil or underhanded, being a network stack hacker myself. The kernel maintainers and core contributers are far from stupid and gullible, and will *not* accept anything if they see proprietary undertones. I'm also sure they're putting a bit more scrutiny into reviewing patches from Novell just because. But the bottom line is more people are working on the kernel, trying to make it better, which is the end-goal. It really, in my mind, doesn't matter who is doing it, just as long as it's getting done and done well.
Just because it hasn't happened doesn't mean it isn't a possibility of happening. If the TSA waited to have something bad happen everytime before they added it to the list of things to inspect, we'd have many more incidents. Granted the shoe inspection is because of the infamous attempted shoe bomber, but that reality check for them prompted other checks.
I get annoyed by the security checks, but if there is a remote possibility that those checks might catch someone really intending on causing something bad to happen, I'm willing to deal with it.
And I'm sure there were a large number of passengers that have the same "techy" level that the TSA agents did, let's not be so hard on those people. I'd rather the TSA agent err on the side of caution than not, and letting something flagrant through screening. Odd that this made the news, when we (society) seem to love pointing out the failures of the TSA of *not* stopping bad things.
One of the things that makes a big impact on performance, on any platform, is the type and speed of memory used. Looking at your list of platforms above, I see an HP Workstation used with the Opteron. Not having one in front of me to verify, but reading on HP's website what chipset and memory is available, you could get a very distinct increase in performance simply due to lower memory latency through the chipset and memory type.
What chipset(s) and memory were used in the Mac's? Were they on-par with a workstation-level machine from HP?
The G5 doesn't surprised me. The underlying architecture, a consumer version of the Power5, is a damn good architecture. But it needs code compiled to use what makes it fast, which is the altivec stuff. I remember watching a G4 right after it released smoke anything on the market with RC5 number crunching *only* if you ran the RC5 passes with altivec enabled. If you ran it with a standard optimization, it got crushed by the Tualatin P3's we had in the labs.
Bottom line is anyone can post benchmark results, but when they don't have a level playing field for their hardware, it's comparing apples to oranges. If the code has any specific code optimizations for any of the processor's respective strengths, then it's apples to oranges. If you post numbers like this, either be prepared to lay out what you specifically used (hardware, software), or be prepared to have long discussions asking for these things. This is why the hardware magazines on the net always use the same application with very well-published hardware setups, so they don't get questions and scrutiny like we have here. Apples to apples is what people like to see. Other data is interesting, but is subject to questions.
Cheers!
Care to publish your numbers that debunk all the other hardware sites that are typically AMD-biased anyways?
And pointing out that it isn't fair to compare because a Core2 duo already executes the full SSE instruction in one pass vs. the 2 clocks for a curret AMD64 is the same as saying it's not fair to compare the on-die memory controller on AMD's vs. Intel's FSB. But people didn't seem to care when the numbers went in AMD's favor.
I'd really be interested in seeing your numbers, your programs, and what compiler options you passed when building on each platform (as well as type of memory, mobo chipset, etc., in each machine).
Broadly waving your hand and stating that it's easy to come up with a new design for the new model is rather naive. While the physics may have not changed, be rest assured the operating conditions, or even the requirements have. Apply this logic to the AK-47. If Kalashnikov just "used the previous model" as a basis of development, who knows what we would have gotten. Instead, he looked at what existed to say what wasn't needed anymore (warfare had changed from long-range firing to more dynamic, medium-to-short-range fighting), and took 4 years to design, build, and have the AK-47 adopted as a main-stream weapon. And 60 years later, it's still in use, with the same design as it had back then.
The US military had a similar experience with the M-16. Very reliable gun, it took a long time with *tons* of testing by the military to adopt it. If you're interested, read this: http://en.wikipedia.org/wiki/M16_rifle.
Innovation of a next-generation thing may seem simple, and can easily be brushed off as trivial. But until you understand what really is going on, and why certain things take so long to really perfect, don't push people's efforts and attention to detail to the side.
Being someone who's survived both a nasty car crash and a moderate motorcycle accident, I have to say I agree with both the laws for seat belts and helmets, respectively. I know that people think seat belts are a pain in the ass to wear, and helmets aren't "cool" when pimping your ride, but as an anonymous motorist that has the unfortunate accident involving one of the former, having a bit of safety in those vehicles might prevent someone from having an accidental death on their conscience. If you happened to drive through an intersection with a green light, but someone not paying attention drove through, not wearing a seat belt, and was launched from the vehicle and killed after you hit him/her, I really don't care who's fault it was, etc., or how much your insurance costs; the fact is that person will have to live with the fact they were responsible - not at fault - for someone's death. That is worse than any insurance hike, etc. It's not just you on the road being "inconvieneced" by a helmet or seat belt law; it's for the peace of mind of everyone else on the damn road you might kill or be killed by because of some unfortunate accident.
Now, if someone is detached enough to be so involved with crossing a street and not seeing a car or bus, ask a motorcyclist how many times they've been cut off by a car that "didn't see them." It goes both ways.
I fortunately don't speak from experience, but I relay from friends of mine that unfortunately have experience in this department.
The patent surrounds the method of storing data on an device to persist indefinately. I want to know any hardware vendor today that makes some form of silicon or any other storage medium that lasts indefinately, or one that has announced plans to make such a device. Microsoft has some really interesting things coming out of their research labs, but this one makes me scratch my head, since they are not a hardware company, and no hardware company has anything remotely close to handling this research. While it's very interesting to be thinking of these things, I don't see why this is a big deal as compared to any other research project any other technology company may be working on.
/. Compare this to all research being done in quantum computing arenas, where some rather radical advances and theories are being pursued, way more radical than this. Do you read about them here? Not usually.
Honestly, this is making headlines because whenever Microsoft files for obscure patents that their rather talented architects and strategic planners can forsee, they are challenged on the basis of validity for their patent. If some startup somewhere was doing this research, it would have never made
Then again, the ol' rock, chisel, and hammer seemed to hold information for a damn long time...
If someone is concerned with traffic shaping, they probably have some clue as to how networks and network flows work. Given that, if they can't figure out how to use the interface to the various QoS solutions, then 1) they're a manager pissed off their web traffic is too slow, or 2) they just need to spend some time with either interface to figure it out.
I have used tc in Linux very heavily, and it can get complicated when specifying filters. I wouldn't expect someone with no idea of what bandwidth allocation is to use it effectively.
Moore's Law doesn't say the speed of a processor will double every 18 months, it states the density of an integrated circuit (i.e. number of transistors) will double every 18 months.
A few years ago, Intel changed the title of all the software engineers working for the software automation of the fabs to automation engineers. Interesting that the management did that when there was a mandatory market adjustment (increase) in pay for software engineers for that review cycle. They changed the titles right before the cutoff date, and screwed a few thousand engineers out of a mandatory raise.
Luckily, I got out of there before they did this. Shitty though? Yes.
Collateral damage is imminent in war. The coalition forces issued many warnings to the civilians of Fallujah to leave before we hit it full-force. If people didn't leave, then they fall under the collateral damage figures of war. I'm not saying this to condone any civilian losing their life in the cross-fire, but shit happens in war.
As far as I can recall, Saddam ordering the deaths of civilians was *not* in a time of war. Therefore it's not collateral damage, it's murder.
Just speculation, but the fact the layout of the motherboard to prevent clutter is more significant than you'd think. In systems with bleeding edge components, you will have components that will still be pulling a generous amount of power. If you have cluttered cables around main airways across the motherboard, you don't remove heat as fast as a well-designed and channeled system. If it's really bad, then you can overheat the machine and have components shut themselves down, or clock themselves down.
Something as little as component layout can make a huge impact.