mashable.com — Back in December, we discussed Google?s decision to shift focus away from Gears, its platform that allows web apps to work offline ? instead the company would utilize HTML5. In the Gears API Blog this week, Google has reinforced that decision, making it clear that the company ?will not be investing resources in active development of new features."
Feb 20, 2010 View in Crawl 4
klijFeb 22, 2010
That really grinds my gears.
scanman20Feb 22, 2010
So should having a username like DudleyDoowanker.
culytFeb 22, 2010
@B1665r: Yeh its freaking deathbead. It's only already supported in just about every major browser (other than IE but thats never going to happen correctly with them pushing SilverLight), clearly it's doomed.If W3 self destructs, HTML5 will still continue, it will just be a joint operation between Google, Mozilla, Opera and whom ever else decides to play nice. It would probably be better to push out Adobe who clearly have a conflict, and replace the old standardization system with a new opener one. W3 don't have a web browser (well a proof of concept one, but not one that anyone cares about), there standards are only useful if browsers and webdevs decide to follow them, that will only happen if they are open and useful.Also this 'committee falling apart', is it anything other than Adobe making a single push to try and block Canvas2D? And Nokia/Apple trying to block the video codec (which I believe might have been backed off on now with Ogg being in Chrome and Mozilla for a while now)? The standard is *much* more than that, those are just a few pieces of bling.
falserFeb 22, 2010
Wow I can't wait to get started learning GWT.
xerathFeb 22, 2010
Yeah, you're wrong. The spec you so kindly linked only affects parsing, document handling, security contexts. The javascript APIs like Application Cache, local storage, and web sql databas, which Gears implemented are not intrinsically bound to html parsing, and anyone with to fingers of forehead will understand that.