Google’s new brower, Google Chrome, certainly isn’t a new thing. But it is only recently that Google have finally released a version for Mac OS, so I’m a bit late on this particular bandwagon.
Chrome is based on the WebKit engine, which is the same engine used by Apple’s Safari browser. WebKit used to be a little ropey but ever since the release of Safari 3 it’s actually been very good, certainly comparable to the quality of the Mozilla engine, which is what Firefox is based on.
Development tools are the same as Safari’s (the WebKit Inspector). These aren’t quite as well developed as the Firebug plugin for Firefox but they do an adequate job. I use Firefox to do most of my development with anyway and then test and modify sites to work in Safari (and other browsers if necessary).
There are of course a few niggles. If a page contains advertisements and an ad-server isn’t responding, this can cause Chrome to believe that the entire page is broken and it will refuse to render the page, eventually killing it off as a non-responsive tab. It would be better to ignore problems generated by loading content from non-responsive servers if they are not the same server from which the main page is being loaded.
The design of the master window means that most of the time you can never read the full title of a web page, since the title of each page is only displayed within the tab, rather than the title bar of the window, which in Chrome does not exist. This can be a little annoying when, for example, you have multiple BBC News pages open, since the title of each one is prefixed with “BBC News | Section name | …”, which usually takes up the whole width of the tab, meaning that all BBC News tabs appear labelled the same in the tab bar.
Other than that there’s not much to moan about and I’m sure it’ll improve with further development anyway. I would recommend it to anyone who’s tired of their existing browser, especially Windows Internet Explorer users. It’s available for Windows, Mac OS and Linux.