Catch up on stories from the past week (and beyond) at the Slashdot story archive


Forgot your password?
Programming Google Technology

Google Phasing Out Gears For HTML5 35

Kelson writes "Have you noticed that there haven't been many updates to Gears in a while? That's because Google has decided to focus instead on similar capabilities in the emerging HTML5 standard: local storage, database, workers and location cover similar functionality, but natively in the web browser. Of course, since Gears and HTML APIs aren't exactly the same, it's not a simple drop-in replacement, so they'll continue supporting the current version of Gears in Firefox and Internet Explorer. I guess this means the long-anticipated Gears support for 64-bit Firefox on Linux and Opera are moot."
This discussion has been archived. No new comments can be posted.

Google Phasing Out Gears For HTML5

Comments Filter:
  • by eihab ( 823648 ) * on Saturday February 20, 2010 @01:41AM (#31208108)

    This just goes to show how much IE is holding us back. According to the Blog post, Google won't be dropping Gears' maintenance support for IE for the foreseen future:

    We will not be investing resources in active development of new features. Likewise, there are some platforms that would require a significant engineering effort to support due to large architectural changes. Specifically, we cannot support Gears in Safari on OS X Snow Leopard and later. Support for Gears in Firefox (including 3.6, which will be supported shortly) and Internet Explorer will continue.

    I'm guessing they'll want that around as a fall back for IE when they start depending more and more on HTML5's new features.

    Had IE been keeping up with HTML5's development, we wouldn't be in a situation where we need external plug-ins to make sure our Apps are cross-platform.

  • by Daengbo ( 523424 ) <> on Saturday February 20, 2010 @04:25AM (#31208644) Homepage Journal

    There's a difference between implementing proposed components [] of yet-to-be-gold standards or specifications and implementing whatever the hell you feel like [] and expecting everyone else to conform. You can see that, can't you?

  • by FlyingGuy ( 989135 ) <flyingguy@gmai l . c om> on Saturday February 20, 2010 @02:05PM (#31211218)

    Once again, we have the guy writing the spec or at least the maintainer working for a company with a HUGE vested interest in its outcome.

    Sorry, but this is no different from MS, IBM or Oracle trying to define how things are going to work and doing it in their best interest.

    Gears was invented to address the hideous short comings of the DOM, and now they think that HTML 5 is the magic pill?!

    Read the HTML 5 spec. It is a rewrite of all the other equally hideous HTML specifications.

    No one, not Google, not the WC3 is doing ANYTHING to fix all the stupidity that is the DOM, HTML and CSS.

    We need to just call it a day on the current state of all of them and start over.

    We need to stop having wars about tables -v- divs and things like What is a construction element and what is a cosmetic element and will CSS effect that part of DOM or not.

    Microsoft was right in a lot of their decisions about how IE would work and present information to the browser user, but as usual they did in the most asshat manner possible and therefor they were wrong, but a lot of their concepts were spot on.

    People keep trying to turn a text rendering program into what is essentially database UI where you can define fields and bind them to data sources. The combination of the two is absolutely insane and should be stopped right now.

    The Browser makers should take a lesson from from from Delphi and VB and just implement a forms painter with objects that handle all the use input and stop trying to build all this crap out of a really really awful mashup of HTML, Javascript and CSS because while it might kinda sorta work, it works like crap.

    A grid control should be implemented that is data aware ( local storage whatevah ) that can properly handle the concept of records instead of having to do all the stupidity you have to do now.

    You want an application UI then build it like one and stop all this insanity of mixing them together.

    I have said it before and I will say it again, there should be two top tags, <HTML> and <APP> and each one tells the browser to do two very different things.

The other line moves faster.