Chrome is smooth, well refined (as of limited usage I have done) and manages the migration process flawlessly by importing every bit of important data from IE or Firefox. The innovative placement of tab bar, lack of title bar (that’s right, no title bar for Chrome), omnibar (that is what Google calls Chrome’s search-cum-address bar) are all a fresh breath of life in an otherwise plain browser. Did I tell you Chrome follows Firefox shortcuts (mostly)?
I had upgraded to WordPress 2.6 today (late, I know), and clicking on the Turbo link did not prompt me for any annoying Gears installer – Gears is built into Chrome.
API support is coming, says Google. APIs will enable developers to write extensions, though the effectiveness of future extensions will have to be seen to be believed. We do have the example of Opera widgets failing completely, now don’t we?
Google Chrome: Screenshots
The installer file downloaded from Google Chrome website is only ~500 KB in size, but launching it downloads the actual Chrome installer (~7MB) from Google servers.
Importing settings is very straightforward, and reminds the import process of Firefox.
Starting up the browser gives you a page like this:
And here I am, writing about Google Chrome (this post) from within Chrome.