The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Abel Avram on Dec 01, 2009
Google seems to be no longer interested in further developing Gears, promoting HTML 5 instead.
In an bug entered for Chromium on Mac OS, Issue 13161, having the description “Gears is not supported”, Mike Pinkerton, Technical Lead for Google Chrome for Mac, commented: “we're not supporting gears on mac in favor of HTML5 additions.” The bug’s status is “Won’t Fix”. So, the upcoming version of Chrome for Mac will no longer use Gears for certain operations like offline browsing or drag and drop.
The reason mentioned by Pinkerton was favoring HTML 5 which will offer offline browsing and the rest of the features currently available in Gears. The problem is that HTML 5 is still far from being fully standardized and IE is still not supporting it. Google’s move shows its confidence in HTML 5’s chance to succeed, and even Microsoft will include some of it in IE 9.
In the meantime, L.A. Times reported that a representative wanted to clarify Google’s position on Gears:
We're continuing to support Gears so that nothing breaks for sites that use it. But we expect developers to use HTML5 for these features moving forward as it's a standards-based approach that will be available across all browsers.
That means Google will continue to fix bugs in existing Gears code but they won’t add anything new to it. Developers will get the idea: move to HTML 5 if possible.
Mobile and the New Two-Tiered Web Architecture
Agile Development: A Manager's Roadmap for Success
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
18 agile and lean practices for effective software development governance
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
No comments
Watch Thread Reply