Development, Privacy, and Standards for Chrome

Continuing our coverage of Google Chrome, snydeq points out an Infoworld story about looking at the new browser from a developer's perspective, and another about how WebKit should be the focus of development efforts, rather than the browsers that use it. TGdaily notes that Chrome's search box will fetch all types of data, and can be made to display banking information with little effort. ABC and coderrr have slightly more paranoid articles questioning Google's commitment to privacy. NetworkWorld suggests that Chrome's unique process model (explained here) will require the development of new measurement standards.

Comments

Re:Gears and the storage API

[Simon (S2)]

The webkit implementation in Chrome right now is over a year out of date...

No conspiracy theory here. Wait for Google to update the current webkit version.

Wabkit has the local storage api in place since Friday, October 19th, that's a pretty long time for a HTML rendering engine, and without backporting stuff to their local implementation.
No conspiracy theory here: companies pushing their own stuff over standard implementations is pretty normal stuff.