Wrong. Read the article s/he linked, it's pretty interesting.
You and the quarter might be nuked before it hits the ground. Ridiculously small probabilites still subtract from the probability you stated of 1.

'era of the gui' - false premise, too. You can have both, as it should be.
It would be great, however, if all GUI apps were designed with a client shell component and the gui just manipulated the command line part for you.

The article says the shooters caused the fire, and then unsuccessfully tried to put it out. I could say "two angry mormons started a fire" and spin the story a different way, too - although I'm sure we can all agree being mormon has nothing to do with causing a fire.

My point is, at no point to they say in the article how the fire was actually caused. I want proof that somehow the action of using their firearms caused a fire.

There is absolutely no way some guy firing rounds into any kind of grass caused a fire. I want proof. I've fired of a ridiculous amount of ammunition, of all types, into all kinds of things since I was a little kid. The only time I've ever seen a fire cause by any kind of round is incendiary rounds or a metric crapton of tracers pounded into a target in short order by a minigun.

Prove it.

Ah yes - the hash is the same. That's the part that matters!

Question - how do you get passwords back from one-way hashes, given that each hash can be generated from an infininate number of original values?

What are you going to do with millions of password hashes, even without usernames none the less?

Tinsnips. No, it's not a sexy purpose-built anit-clamshell device, but it might as well be.
Seriously. $6 for a pair at Walmart, they will last a lifetime of clam shell cutting.

My thoughts exactly. When I notice things like this, I tend to take every other assertion by the author with a grain of salt.

There does not appear to be an effect of any kind on the difficulty of the material in an article, i.e. how much of the Slashdot audience is likely to understand it, versus the rate and amount of comments.

I draw the conclusion that the bullshit level must rise, given everything else remains constant.

Profiteering at the expense of customer experience = short term gains, long term losses.

US DOD - "Fixing our economy one giant military expenditure at a time."

Is it overpriced - most definitely. But this is Slashdot, and you have a company trying to make a commercially successful PC with Linux on it. Why is this a problem?
The original article had an obvious hard slant against it - let's try and think for ourselves a little here.

DISCLAIMER: I type this on a Windows box, but I have a vt420 connected to an Arch VM sitting next to me :)

But I'm more comfortable with real numbers.
I mean, _clearly_ they would save at least $3000 because they would reduce the manufacturing cost that can be had for usually $4000.

Compare the $1000 savings... much better than paying just $1200 for the dealer option. I mean, that's more than 20% off.

And who doesn't want more than 20% off?

You don't know something is disruptive before it comes out. It's disruptive when it comes out and actually disrupts.