The Future of Google Chrome

TRNick writes "Lars Bak, who heads up development of Google Chrome's cornerstone javascript engine, talks about why Google is so focused on in-browser javascript performance, the role Chrome has played in driving up javascript performance in other browsers, and why it's taking so long to introduce support for third-party extensions. 'The web is becoming an integral part of the computer and the basic distinction between the OS and the browser doesn't matter very much any more,' he says."

Comments

Re:How Many People Even Use Chrome?

[jitterman]

Call me ignorant, or rash, or just living on the edge, but I actually use it on a daily basis for *almost everything. I haven't installed FF on this (brand new) machine and don't plan on it simply due to its bloat and slowness - things it didn't have when it was introduced.

Chrome introduced features which IE and FF either have since included as well or are planned for future releases. I am certainly aware that Chrome is quite limited in some areas, but in the end its speed, flexibility, small memory footprint, and physical layout (minimal intrusion into the web page display area) make it my first choice despite its drawbacks. Feel free to correct me where I may be ignorant (seriously, no sarcasm intended).

*Every now and then I find a web app that's just not well coded (mostly due to funky CSS that's poorly formed) that works or at least displays properly in IE but not Chrome. C'est la vie.

Re:As we've seen.

[pixelcort]

Too late. Google Docs is already here, a JavaScript word processor with real-time collaboration features.