But what about countries other than the US?

Not sure simplicity is an issue. Once the filesystems are set up, it's no harder to manage two than one, and set-up is a one-off operation. No reserved blocks also means you aren't paying for storage that rarely gets used (on the assumption that users use more blocks in normal use than root needs IFF all other blocks are used).

Still amazed (and pissed off) at the number of websites whose developers reject sub-addresses.

One reason for separating out /var and /tmp at least was so that if some jackass^Wuser trampled all over /tmp (dd if=/dev/random of=/tmp/what_fun bs=10240 count=1000000), that didn't stop the system from logging to /var. Similarly if /var gets hosed in some fashion it doesn't stop the rest of the system from being used while fsck is run.

Here's a fun and simple way to teach your kids the value of money. "Hey, Coren22 Jr, do the dishes and I'll give you $1." At some point, Coren22 Jr figures out that $1 is not an appropriate reward for the thrill of loading the dishwasher, and says "Ok dad, but this time it'll cost you $5.". Achievement unlocked: Parenting 101.

The experience of an apple product? You mean the spinning beachball? Or the fact that when using Spaces, the OS will switch to whatever Space it feels like, somewhat arbitrarily, if there is an app running in that space that thinks it has something to tell me? Or the oft-experienced refusal to unlock the screen after accepting the password, beeping at me because I dare try to wake the thing up? That experience? You can keep it - I'll take cold and functional over warm and broken any day when it comes to computers.

GP doesn't know the difference between cue and queue; went halfway.

I'd love to live in your world, where success is only measured by the failure of others. Seriously, what does saying "and doesn't just buy start-up companies like Google does" add to your point?

Why the first-owner-only warning? Resale would-be purchasers deserve the same warning. Put it in the same place as the airbag warning and prevent its removal.

I'm just gonna throw a big fat NO out here to anyone that thinks documenting WHAT code is doing is a good idea (as opposed to WHY it is doing it)*. If you have a comment to explain WHAT the code is doing, and the code gets changed, how many engineers bother to even read the comment, much less change it? Documenting the WHY allows the implementation to change while still passing on the required information - what is the business reason driving this code?

* - Exceptions are for particularly gnarly code (that can oftentimes serve as a placeholder to get something done - and should generally be of the order of a dozen lines at most) and for code that defies the official word (such as a call to an API whose own documentation states 'X returns an array' but that in reality returns a single datum).

Pretty sure any Perl Jedi worthy of the name would know it is correctly capitalised perl or Perl.

Interestingly enough, the DRDD installed an ATM machine that you didn't have to enter a PIN number into to access your cash.

The was a time when battles were fought starting at dawn and ending as the sun went down - to fight during the night (even/ especially with guerilla tactics) was unheard of - it simply wasn't civilized. This led to a number of spectacular defeats at the hand of an enemy who did not share the same philosophy.

I believe the same process applies to terrorists not changing their names to something less conspicuous - it simply doesn't fit with their way of thinking. It's not a matter of being dumb (or not), it just isn't the right thing to do. Perhaps when you live or die on the belief that 72 virgins await you only after you perform the ultimate sacrifice, holding on to your real name is important. Otherwise, the wrong John Smith might get your virgins!

Where the fuck do you work that employees can't be fired?

So: you've seen the impact on one kid of shitty parents, and you extrapolate this to all pot use, without a single shred of evidence that pot was actually the problem in this single, isolated case? I salute your faultless logic.