What Google Chrome means to web developers
With the release of Google Chrome just coming up tomorrow, by now the blogosphere should be on fire with all the screenshots and juicy details. Even though I see Google Chrome as something that means more to the user than to the developer, there are certain goodies in Google Chrome that aim to provide a better platform for developers. What's the implication for web developers here?
- A stronger push for WebKit. This addresses some moans I saw on Digg (or is it Slashdot?) that could basically be summarized as "oh, great, now we have another fugging browser to debug." Google chose WebKit as the rendering engine for Chrome, so as a web developer, if your current pages and apps work on Safari, it's probably going to work fine on Chrome.
- Gears included. Just having a better JS engine doesn't seem enough for Google, so they also included Gears, which provides developers a client-side database storage to enable offline usage for web apps.