In all this hullabullo over Chrome, it’s a delight to come across voices that see through the clutter. Came across one such voice in a comment on Chrome by Josh Jonte
Now, imagine if Google Gears ran on Google App Engine. Instead of persisting the database in the browser (Sqlite), it persists to BigTable. You would be able to spawn things like worker threads, timers, and http requests. What would it take to run Gears on the server? A high performance dynamic language runtime, a la V8. V8 could potentially run any dynamic programming language, the constructs are similar among all the languages (closures, dynamic typing). App Engine runs Python ATM, Python is a dynamic language. So V8 could be the runtime powering App Engine *right now*.
So the same runtime in the browser, your phone, and the server. All using the same library, Gears.
That’s why they need to compete so fiercely in the advertising – they need to subsidize (replace?) the loss of people paying for their software.
At the end of the day, it’s a competition for the Enterprise. Assuming both Microsoft and Google get their data-centers compliant with all the privacy regs (HIPPA, FERPA), they want the enterprise to run their vertical and niche applications on Google or Microsoft cloud.
V8 + Gears vs. Silverlight
Ironically (maybe not), Chrome is really just that for Google – it’s just chrome for their runtime.
Funny thing is, I don’t Adobe knows what they’re getting themselves into with AIR