It's interesting to see folks I've meet online flood my IM's, Email Accounts etc with "Did you see Google Gears, how cool is this!!"

I got the same reaction from JavaFX, Apollo, Silverlight and so on. I often look at these things with one eye brow raised, and I do this not to attack anything not Microsoft specific, but I'm trying to figure out what's in it for Google. It's my immediate reaction, as a company of that size would not sit on something like this and then unload onto the world without a reason.

Let's take a look at what Google Gears expected to do:

  • A local server, to cache and serve application resources (HTML, JavaScript, images, etc.) without needing to contact a server
  • A database, to store and access data from within the browser
  • A worker thread pool, to make web applications more responsive by performing expensive operations in the background.

My initial thoughts are "wow, offline / online connectivity, that's good!". Yet then I started to think about applications I would typically write with such ingredients. Let's assume I wrote a simple Calendar Tool, where I can plan out my month while I'm on the plane (as that's were we all seem to do the most work - never been able to unfold a laptop on a plane, except business class but anyway). I punch in all my details, and it stores them locally.

I then arrive into a network friendly zone, hook my laptop up and it magically synchronizes the data for me right? What it doesn't?  I still have to code?.. well.. that's not what the brochure said? (Hey they could very well pull it off, but at the moment it's oversold, over hyped and not enough detail)

I'm sure there will be positive business cases found for it? but what is it really bringing to the table and how many developers are sitting around today going "If only I had occasionally connected client status on laptops! - boy I can't tell you how annoying that is". Usually when they do, it's got a lot more complexity associated to it, and typically there would be much bigger and bolder collision algorithms associated to it.

Do I think Google Gears sucks? nope!, I just simply scratch my head ponder what the hell is in it for Google firstly, secondly me and lastly how will this help me get more runs on the board with development? (especially with Tools interoperability).

Adobe Apollo (YAB) absorbing it sounds positive for Adobe but it kind of looks like a PR push to bolster Apollo's name by cashing in on Google's fame (that's the sceptic within me talking though).

It sounds like Snake Oil in parts :)