... and wwwwrrrrrrrrrrrriggling
I voted CPU, but technically it was the plastic clips holding the heat sink against the CPU getting old and brittle. One of the clips cracked just enough to let the heat sink lift partially away from the CPU and, well... buh bye magic smoke.
What is it that determines whether a jerk sticks around long enough to succeed and become someone at the top that others excuse and follow or is fired with a "do not rehire" mark on his HR record?
"Sometimes people don't understand the responsibilities that CEOs have, so sometimes they'll take that as, 'Why is he being such an asshole?'" Wolff did allow that Pincus sometimes uses language devoid of "soothing qualities," and could be challenging to work for, depending on how you adapted to his management style. "He's moving at 100 miles per hour. You've either got to get on the bus, or you're not on the bus," he says. "Most people have a buffer.
... Mark's not like that. He thinks it, and he says it."
Perhaps the gameplay of FarmVille offers a lesson: you'll put up with shit if you get a little candy now and then, with a promise of a big payout later. Guys like Pincus have a knack for showing just enough promising results (cash profit) to whet the appetite while exploiting the "compulsion loop" of the people they work with. Nice work, if you can stand yourself.
Makes total sense, as Zynga's 'games' are far more like casino slots and other sorts of gambling than real skill- or puzzle-based games.
Bjeat mje tjøø ijt.
I figured any software developer worthy of the title had heard the story and understood the details already, so I merely linked to the Wikipedia article for reference. Yes, the full filesystem was the root cause, but the repeated reboots and failure of commands to the rover to go into night-time shutdown arose from a race condition within a critical sequence. If you want a more technical analysis, you'll find many, but one is http://www.cs.princeton.edu/courses/archive/fall09/cos109/mars.rover.pdf
While no doubt the atomicity of rename() will prop up the code of naive programmers, there's a great deal more to the operation in question than just changing the file name. Once again, oversimplifying the solution ensures that subtle bugs remain. As for the comment "relatively safe", that's like saying a 39-story fall from the roof of a 40-story building is "relatively healthy".
And of course, if your world is only POSIX and Windows, then portability is still an unrealized goal.
Every two-bit peachfuzz-face programmer in the open source world thinks he has the solution to lots of long-standing bugs. Being able to read what a spec says and actually understanding how it works in actual implementations. For example, what's the behavior of rename() if the file is actually a symbolic link? Patches or GTFO.
The fix is trivial: simply write the new config file out-of-place, and then replace the original with it once it has been fully written.
You left out, "and do it in a way that avoids race conditions". You must also do it in a way that is portable, so it can't depend on OS-specific crutches, and is secure and doesn't interact badly with locking mechanisms that may be transparently in place on the underlying filesystem (NFS, for example). Programming 101 may teach you some things, but most assuredly if that's all you know, a "trivial" write-new-and-replace implementation will be worse. If you are so 100% sure you know how to avoid all these problems, there's some programmers who troubleshot a similar race-condition error from millions of miles away who might have even more possible failure modes to throw at you.
September is Cyborg month, and the 18th is Talk Like a Pirate Day. What does that mean?
OK smart boy. The mozilla project is open source. If this bug is so all-fired important to you, get to coding, or because you admit you don't have the skills, hire someone who can code it. Don't go whining "THEY won't fix a bug I care about". This 'bug' isn't going to get fixed simply because the folks who could fix it have far better things to spend time on than working around an arbitrary limitation in a not-too-far-in-the-future legacy 32-bit platform. I would be willing to wager that your assertion that web pages have lots of GIFs any more is false anyway. The PNG and JPG formats have pretty much completely replaced that 80s-era 256-color format.
As a matter of fact, with the introduction of things like infallible malloc, you're likely to see more badly-engineered platforms crashing on crappy web pages.
But again I say, if YOU don't like the bug, then YOU fix it, and submit a patch. If they don't accept your patch, then you can build your own FF from source and patch it however crazy way you want.
And by the way, the wikipedia page on GIF, http://en.wikipedia.org/wiki/Graphics_Interchange_Format, doesn't crash FF 3.6.10 running on OS X Snow Leopard in 32-bit mode. As they say in the business, WORKSFORME.
Comparing 3D tv to color is completely missing the problem. The move to color made sense and was a natural progression that mirrored film. The move to 3d is just another to way to get consumers to consider their old equipment obsolete and force them into buying new TVs. Like a lot of the consumer electronic gadgetry out there, the benefits are questionable at best and the upgrade treadmill only benefits the vendors. Now that they've sold digital to everyone and forced the decades-old standard into obsolescence the electronics makers smell blood. What better way to ensure profits than following the personal computer model of convincing everyone that the perfectly good equipment they bought two years ago is now "outdated" and needs replacing.
Anyone remember the 1981 movie "Comin' At Ya!"? Noted at the time for all the action shots of exaggerated movement towards the camera (arrows, knives, boobies), it was nothing but a gimmick. Sounds like almost 30 years later the salespeople are still pushing the same tricks.
There was a time, in the early days of "horseless carriages" when the law required that a person on foot carrying a flag precede the presumably scary, steam-huffing monstrosity, to warn the pedestrians and horses that the oncoming fuming and chuffing machine of the devil was approaching.
Wear a different hat each day.
I put on my robe and wizard hat.
Karl's version of Parkinson's Law: Work expands to exceed the time alloted it.