One word: allergies

For instance, I personally am allergic to ordinary boned fish, but don't have a problem with shelled fish. So if I order crab, it's important to me to know that it's actually crab, and not imitation crab, because one will make me sick, and the other won't.

I tend to like Department of Homeland Insecurity. Also sums it up rather well, and isn't a drastic change in its name. It's also a lot better descriptively than the current name.

The most optimal one for years has been the one that Bill Gates devised, which would result in 5/3 N number of flips, but now the best solution is only 1% more optimal than his solution.

And funnily, that's really the only known contribution that Bill Gates has done to the field of computer science, well, and a tad bit of programming in Windows 1.0 and the editions of DOS that came before that. After that, he didn't do anything anymore, or at least acknowledge that he did, since he became more occupied with managing Microsoft than coding.

It is the Wii 2, in any case.

And, if translated to Japanese, that makes it the Wii Ni. ;)

Compensation indeed.

Einhorn is Finkle, Finkle is Einhorn?

Er, sorry, I mean "Do what you love, and you'll never work a day in your life", which is even more applicable than what I said originally. :P

You know what they say: If you're going to work, make it something which you enjoy. In this case, we have many agents investigating child pornography. Dunno what to think about that. ;)

And neither of those facts matters to nonprogrammers. It's much akin to just saying "Oh well if you really care about that, there's some configuration file which you can mess around with where those keys are hidden (and you might just need to guess to find out what those keys happen to be)". If the user already has no clue as to how to program, or isn't able to invest a lot of time to learn an interface which might just be deprecated in a few releases due to a cascade of attention-deficit teenagers, who would much rather remove and replace something with their own new hotness rather than try to find out why something doesn't work, then you're screwed.

It'd be much better to try to both enable the user by providing good low and high level tools, instead of trying to constantly try to remove configuration from the low end tools because you don't like users doing anything more than what you think they should do. That's why I stopped using GNOME; because while I can program, I do get tired of the constant battle against what I like or need for my own workspace, especially since efforts like these decrease my own productivity, not increase them.

It's possible that she might be wanting to watch some seasons which haven't been released on DVD yet, and is basing that judgement on full retail price for previous seasons. Which still equates to a marketing failure.

Dunno, seems like a tough call. Hello Kitty was able to do quite a bit to Cthulu.

Easy. The key you're given is only valid for the country the plane is over, and you rotate keys on a regular basis without repeating (and get your key on entry to a particular country/block of countries like the EU). That way, only planes which have already been authorized to go over a particular country's airspace can get keys. The keys don't have to be in the public hands, and you could even have a few hour grace period for transitioning keys so that the planes that were still in the air when the key changed aren't immediately flagged as using an illegal encryption key.

To be honest, it's a surprise that they don't actually do something like this. You still would know that there's a plane there when it responds back, but at least you can't get anything from it without knowing the key being used at that particular time (and leaking keys would only be valid for a limited period of time, which would make it so that they could just change what key to use for a particular interval when they know in advance that their list has been compromised).

Uh... wrong. Even if you tab, it won't indent properly when displayed using other spacing patterns. For instance, if you are lining up some statements that run over the line to make the code easier to read (which is a perfectly acceptable style), then different tab indents could screw that up. Using tabbing to just mask for indenting with spaces isn't a real solution to code indenting because of this, since you're still relying on a set tab spacing anyways in order to make your code readable, even if you don't think you are.

Because of this, what you're saying doesn't make a lot of sense to begin with, and it doesn't pay to try to trivialize the whole spacing debate. In any case, indenting with spaces removes ambiguity in how your code should be indented that tabbing introduces. If you seriously don't think that this is an issue, then you should seriously take a closer look at some lines of code which run over a line. If you've never had this problem, then you've never really done any serious programming before, and shouldn't really be commenting on something which you aren't familiar with.

As a programmer, I could really care less how many spaces a tab represents, or if someone uses tabs vs. spaces, but I do want to see consistency in its use within the bundle of code that I have to work on or consult, since having to switch back and forth for code spacing is going to be a huge drain on readability. And, like I stated before, just telling people to use ambiguous tabs over spaces without a tab to space convention already specified within a style document for your project doesn't do much more than to make the person viewing the code guess how many spaces their tabs represent. It may not sound like a big deal to you, but it can be a big headache when you have to continually switch back and forth between different tab spacing defines because different people like you assumed that a tab will look the same for everyone no matter how many spaces are used. Because of this, I would much rather prefer to define how many spaces a tab should represent in the code style documents for languages which have tabs as part of their syntax (like Python), and unambiguous spaces for everything else, so that I don't have to either guess at what sort of spacing the person used, or to read more style documents than I have to (most are designed rather well so that you can infer the style from code you've already seen. I personally would much rather not have to consult a style document unless I reach a case that seems ambiguous to me. That way, I can focus more on coding what I need to, rather than just reading every piece of documentation that comes my way.)