Ive cut this from here http://gearsblog.blogspot.com/2008/04/gears-and-standards.html:
<quote> Gears is an implementation of web standards that lives inside another browser. For example, the HTML5 Database API might be available to developers through both the google.gears object and the traditional window object. This is OK, and in some ways a good thing. Developers will be able to mix and match the pieces of Gears and native browser implementations that work best. </quote> Is this still the idea? The Html 5 API is currently callback based while Gears API appears to block during db interaction. Is there currently a roadmap for the Gears and HTML 5 structured storage API to merge? Assuming HTML 5 structured storage moves forward as currently specified - will Gears be subsumed by HTML 5. While I appreciate Google's efforts in moving browser technology out of the 1990's, I do not relish another battle between propriety based and standards based solutions. Thoughts? Also I would like any suggestions for mitigating risk when Gears is updated and pushed out to my clients via the browser before I have had time to debug, alter my application to match the new version of Gears.
