JeffreyBarke.net

Jeffrey Zeldman posted a nice overview of Chrome to his blog at http://www.zeldman.com/2008/09/03/a-bug-in-google-chrome/. What's most important, though, is his mention of a bug report by Jeremy Jarratt: "Google Chrome wrongly displays alternate styles as if active, thus 'breaking' websites that use them." (Learn more about alternate styles at A List Apart.)

PPK talks about Chrome at http://www.quirksmode.org/blog/archives/2008/09/google_chrome.html. He updated his BrowserDetect JavaScript object to detect Chrome.

John Resig provides a rundown of the various browsers' JavaScript engine performance at http://ejohn.org/blog/javascript-performance-rundown/. John uses three different test suites and discusses what the tests are testing and how the numbers relate to actual web page performance.

Using the Dromaeo test suite, which attempts to mimic how browsers perform under a normal web browsing situation, the WebKit-based engines came out ahead. Safari has a slight lead over Chrome, then the Firefox engines (TraceMonkey and SpiderMonkey), followed by Opera. No results for IE were provided, because it crashes while running the tests.

Personally, I downloaded Chrome yesterday and love it. The interface is very clean, pages render well and browsing is fast. I'm sorry Firefox, but while you're still my development browser of choice, for pleasure I've been using Safari on the Mac and will now be using Chrome on the PC.