Google Abandoning Gears
harrymcc noted a story talking about what might be the end of Google Gears. The concept has always been interesting, but it seems that Google is beginning to think of Gears as more of a proof of concept, and that focus will shift to HTML5, which has the same functionality.
that's the reason
Saying that Google is abandoning Gears is not 100% accurate as it has bad connotations.
Google created Gears to fill the void until browser makers would implement HTML5. Now that they are doing so, Gears is being retired.
Gears was a smart way to get important new features into stagnant older browsers (we're looking at you, IE...) and implemented far more quickly than any standards process allows. Now that those features are in the HTML5 standard, there's no reason to require gears. Until the next round of feature-adding, of course...
Makes one wonder how much of this "HTML 5 will do this", "HTML 5 will do that" is hype or wishful thinking. Past experience has shown great disappointment in all this hyperbole...
On a beach in Mexico a whale beached itself. It's buoyant fatty body crushed the whale's lungs and suffocated it in the wide open air. Bacteria from the whale's intestines began to multiply and ferment and large amounts of gas accumulated in the whale's body. Soon a bulge was visible around the belly of the whale. Then the bulge grew until the whole carcass was bloated.
One day, the whale's rotting body broke and released the gas in a giant explosion.
Pushing functionality into the browser instead of relying on scripting means longer launch times, more failure points, and more disparate functionality from browser to browser for developers to consider. It's a fountain of whale guts, metaphorically speaking.
...I won't really miss Gears. Since right now Offline Gmail uses Gears, I don't want it to go away.
Google has created a technology to adress the shortcomings of an old standard and now, as the new one reaches it's final state, Google tells us to use it.
that Google Gears would be replaced by Google Sky Net ?
Abandoning gears has been obvious for some time - for instance, there's no support in the linux version of Chrome. However, the question is, when willl existing google services based on Gears move to HTML5? The most important one of these being, of course, offline gmail. Google has demonstrated a mobile offline gmail prototype using HTML5 around the beginning of 2009, so the delay is hard to justify on a technical basis.
One wonders if they haven't made a policy decision not to support offline gmail - to force you to use the online, ad-containing version. If that is true, it would be yet another straw on the back of the "don't be evil" camel.
Preferential Voting: easy as 1-2-3
event the iphone app is just a front for the website. For Google Reader I use MobileRSS that downloads the first few lines of my feeds so i can read them offline in the NYC subway.
Come to the Dark Side of the Force.
I had poor luck successfully using Google Docs offline, even though this was supposedly what Gears was made for. I still do find Gears useful for one thing - Wordpress. I obviously can't blog offline, and if I were writing a post offline I'd do it in Microsoft Live Writer or MS Word or something, but regardless, that's not how Wordpress uses Gears; it leverages Gears to cache common Javascript files locally so that the pages on the admin console load much more quickly. This makes complex procedures really painless - like when I have to switch between many pages on the admin console, such as when I'm tweaking a series of templates or testing incremental changes to a plugin.
I'm no web designer so perhaps I'm misunderstanding TFA, but is offline script caching one of the features of HTML5? I really love this feature for frequently viewed web apps.
shift gear
So now, with a browser having 100% perfect Acid 3 score even on mobile/ARM flavor, I should be able to use Google sites in their full function not missing a single feature, no quirks, no "browser.js" hacks.
Basically I should be able to use Opera 10.10 and I shouldn't be thinking a second about Google Chrome which wasn't released for PowerPC anyway.
Somehow, I have hard time believing that.
I'd been toying with the idea of making my existing webapp available offline, and just this morning began reading up on Google Gears to use it. I put the documentation down for a minute to check out /. and what do I see? Well, fuck.
The couple of times I looked into Gears, the main feature touted by Google was the ability to use your web apps when you're not connected to the internet. This was reason enough for me not to spend a lot of energy on Gears, as in practice, in this day and age, I never find a computer that is NOT connected to the internet.
So in short, I've never had a need for Gears.
He who laughs last, thinks slowest.
We don't even imply that MS had any original ideas around here.
Hey if your going to mock, do it correctly. Need to output an integer? Use assembly instruction code to write to hard-coded address. Done.
From what I understood, Gears was the primary reason a computer with chrome OS is somewhat more useful than a brick when offline. Does this mean they'll have to allow real local applications for chrome OS now?
Evil Evil Evil!
One of the more overlooked features of Gears is its JavaScript parser, which allows apps to execute JavaScript in a separate thread from the rest of the page to improve performance. Now that Google has released Chrome, it makes less sense for it to keep working on a hack to allow Firefox and IE to run JavaScript more efficiently. Chrome is incentive enough for Mozilla and Microsoft to start doing that for themselves.
Breakfast served all day!
Which part of this is it that Google != do no evil?
me.bows_down_to(Google)
http://www.debunkingskeptics.com/
Gears went out of favor after Babbage's Difference Engine.
Have gnu, will travel.
does this mean I can't save my content on google locally any more, and access it off line?
IE6 lock-in is not a myth. My company Integrien.com has developed a very powerful web based application using as much of the latest tech is possible. We though we could completely abandon IE6 for the new features, we where some what wrong. At lease 70% of our customers where OK with IE7+ or Firefox 3+.
The problem for corporation is the following: for those that jumped on the web bandwagon early have create 1,000 of applications that run in only older browsers.The cost to upgrade all those applications would be very expensive to upgrade and test and they work now. So for some of our users IE6 is the highest they can get to. We had to go back and write some work arounds for this limits.