Carl Franklin, co-host of the popular ".NET Rocks!" podcast has a great show about this very subject. http://www.dotnetrocks.com/default.aspx?showNum=768 Don't worry, it's not Microsoft focused. You really should have a listen. He actually went to Washington DC to get involved. That's more than most of us can say.

Doesn't invincible imply that it CAN'T be destroyed? Oh wait, they cased it InVincible, nevermind...

So they love NoSQL but had a bad experience with CouchDB. And the solution is... move away from NoSQL??? Ridiculous. CouchDB is certainly NOT the only solution out there, and they all have their strengths and weaknesses.

I've recently switched from MS SQL Server to RavenDB http://www.ravendb.net/ and I am never going back! Many of the things they found wrong with CouchDB and MongoDB are superior in RavenDB.

Not sure about MongoDB or CouchDB, but I have experience with RavenDB, which is absolutely fantastic. Instead of "joins" you have "includes" or "live projections". See http://ravendb.net/docs/client-api/querying/handling-document-relationships

Or explaining that to the TSA on your next trip to grandmas house.

I would think the downfall of a system like this is that it would require user training for each and every gesture. Certainly, humans of different ages and hand sizes would have different capacitive properties to their hands. I'm sure other factors like body hair, perspiration, skin tone or texture, etc. probably have some affect.

If training WASN'T required, I could see Disney using this in their theme parks. Especially in the little kids rides and houses in Mickey's Toon Town. Imagine the surprise on your four-year-old's face when the fake plastic props start interacting with them in interesting ways.

I'm pretty certain training would be a requirement though. And alas, you aren't going to get a four-year-old to sit through a calibration session.

Maybe this has better applications for the deaf or blind as a more precise haptic interface to other devices.

With winds that high, and no gravity, you'd think the surface would erode to nothing and dissipate into space. I call BS.

"To the cloud!"

The best part is how the plaintiff claims that their case depends on "Section 63" of the CPC act. There is no section 63!
http://laws.justice.gc.ca/eng/acts/C-10/

assignment: x =
comparison: x ==

There, fixed that for you.

I agree to a point. If you want some real insight, check out how the folks working on noda-time (a .Net implementation of java's joda-time library) have described the issues with .Net's built-in DateTime handling: http://noda-time.blogspot.com/

Although, nothing described there would account for this leap-day bug. My guess is that some developer decided to do his own math on dates rather than using the framework's implementation.

I think it's a mistake to say "oh, well everyone's got it wrong so don't trust a library". You probably can get more out of a library than doing it yourself. However, you have to be aware of the implications of using that library.

On the .Net platform in particular, Microsoft has made a mess of things by making developers think that DateTime, and TimeZoneInfo are "perfect". They're not.

I don't know, but I'm sure it has something to do with Cialis.

Why the hell would you give the guy at Kikos a box of your tax returns and legal documents? Especially since you are asking him to scan them! It only takes a minute for him to make his own digital copy and poof! There goes your identity.

but next thing you know you're in a helicopter, shooting monkeys off the Golden Gate Bridge with a machine gun.