I doubt al Qaeda had any intention of this bomb going off. They put it in somebody's underwear, just so Americans would now have to strip to get on a plane. Government officials need to stop going on TV and saying that the terrorists "hate freedom." Because they do. And if the terrorist's goal is to attack freedom, guess what, government? YOU'RE LETTING THEM WIN. Put an X-Ray machine, a Geiger counter, and a dog at every terminal in the country. That's it. When the terrorists have a bomb that isn't made of metal AND is made of a chemical the dog can't detect, send a sample of that chemical to every airport in the country, and teach the dogs to smell that too.

"To quiet privacy concerns, the authorities are also spending $7 million to 'remove the human factor from the image review process' and replace the passenger's image with an avatar."

http://www.imaxmelbourne.com.au/images/uploads/Avatar/Avatar-BIG-1.jpg

"Sorry, buddy, you're gonna have to check that bow."

The NFL needs to set aside a SUSBTANTIAL of their $9 billion cash flow to researching better helmets. I don't mean moderate improvements. I'm talking about something that can wick away nearly all of the impact force to other parts of the body. This is the single biggest existential threat to the game, and it has got to be resolved.

It would take a lot longer to look up Romney. You'd have to search all 5 or 6 of his houses.

Issue is, it's not a convention. Half the apps out there do 2.9 > 2.10, and half the apps don't. So unless you go back and read the version history for an app, you can't be sure which format it's using. It's the inconsistency I don't like, more than the practice itself. If every app out there did 2.9 2.10, you could get used to it. If it's, "Well, which way is this one set up?" then that's unclear.

What makes it frustrating is that some developers DO use decimal notation because they're actually using decimal version numbers, and so if you're not familiar with the release cycle of a program, it can sometimes take a minute to figure out if they're on decimal numbers (2.9 > 2.10) or on separators (2.10 > 2.9). Things like IP addresses and dates are consistently written in that way - you don't sometimes do math on the octets and other times not. Thus, not confusing. It's the inconsistency that bothers me.

Understanding, and agreeing with, are two vastly different things. I emphatically disagree with the practice. Which I can only do because I understand how it works, and find it to be a poor method.

Emphasis.

While I'm not a fan of MS numbering, at least it's a number that keeps going up.

Jesus Christ. Now I remember why I never post here any more. Seemingly everyone who posts on tech forums feels that having survived being the nerd that nobody wanted to talk to in school gives them the right to be an abject, vitriolic prick on the Internet, where nobody can see that they're living in their mom's basement and having a monogamous relationship with a tube sock.

Of course I -understand- how version numbers work. I've been designing software for 17 years. The point I'm making is that the way these companies are doing the version numbering, while understood, is dumb. If you're going to write a number like a decimal, it should be a decimal. When you increment up from 2.9, you should go to something like 2.91, or FSM forbid, 3.0. Secondary decimal points are ridiculous to me. If you want to reference a build number, put it in another field somewhere - nobody really cares about the build number unless that's all that changed, meaning it's probably a development snapshot rather than an actual release.

So, to review for you dickless trolls out there, understanding does not equal agreement.