Google Chrome – First Impressions

First impression: Google delivered, I’ve never used a browser this fast. It’s great.

Yesterday, a cartoon was prematurely leaked detailing Google’s vision for what a browser could look like. Now, 24 hours later I’m reviewing what until yesterday was a well kept secret.

So here’s my first impressions.

  • Fast and responsive. What can I say? Firefox 3 was an improvement over Firefox 2 but this is in a different league. There’s still lots of issues with having many tabs open in Firefox. I’ve noticed it doesn’t like handling bitmaps and switching tabs gets unusable with a few dozen tabs open. Chrome does not have this issue at all. It’s faster than anything I’ve browsed with so far (pretty much any browser you can think of probably).
  • Memory usage. Chrome starts new processes for each domain and not per tab. I opened a lot of tabs in the same domain and the number of processes did not go up. Go to a different domain and you get another chrome process. However, it does seem to use substantial amount of memory in total. Firefox 3 is definitely better. Not an issue with 2 GB like I have and the good news is that you get memory back when you close tabs. But still, 40-60MB per domain is quite a lot.
  • Javascript performance. Seems fantastic. Gmail and Google Reader load in no time at all. Easily faster than Firefox 3.
  • UI. A bit spartan if you are used to Firefox with custom bells & wistles (I have about a dozen extensions). But it works and is responsive. I like it. Some random impressions here: 
    • no status bar (good)
    • very few buttons (good)
    • no separate search field (could be confusing for users)
    • tabs on top, looks good, unlike IE7.
    • mouse & keyboard. Mostly like in Firefox. Happy to see middle click works. However, / does not work and you need to type ctrl+f to get in page search
  • URL bar. So far so good, seems to copy most of the relevant features from Firefox 3. I like Firefox 3’s behaviour better though.
  • RSS feeds. There does not seem to be any support for subscribing to, or reading feeds. Strange. If I somehow missed it, there’s a huge usability issue here. If not, I assume it will be added.
  • Bookmarks. An important feature for any browser. Google has partially duplicated Firefox 3’s behaviour with a little star icon but no tagging.
  • Extensions. none whatsoever :-(. If I end up not switching, this will be the reason. I need my extensions.
  • Import Firefox Profile. Seems pretty good, passwords, browsing history, bookmarks, etc. were all imported. Except for my cookies.
  • Home screen. Seems nicer than a blank page but nothing I’d miss. Looks a bit empty on my 1600×1200 screen.
  • Missing in action. No spelling control, no search plugins (at least no obvious way for me to use them even though all my firefox search plugins are listed in the options screen), no print preview, no bookmarks management, no menu bar (good, don’t miss it)
So Google delivers on promises they never made. Just out of the blue there is Chrome and the rest of the browser world has some catching up to do. Firefox and Safari are both working on the right things of course and have been a huge influence on Chrome (which Google gives them plenty of credit for). However, the fact is that Google is showing both of them that they can do much better. 
Technically I think the key innovation here is using multiple processes to handle tabs from different domains. This is a good idea from both a security point of view as from a performance point of view. Other browsers try to be clever here and do everything in one process with less than stellar results. I see Firefox 3 still block the entire UI regularly and that is just inherent to its architecture. This simply won’t happen with Chrome. Worst case is that one of the tabs becomes unusable and you just close it. Technically, you might wonder if they could not have done this with threads instead of processes.

So, I’m genuinely impressed here. Google is really delivering something exceptionally solid here. Download it and see for yourself.

Posting this from Chrome of course.


I’ve been enthusiastic about openid for a while but have so far not managed to openid enable my site. WP-OpenID, which is the main openid plugin for wordpress is under quite active development. Unfortunately, until recently, any version I tried of that had some issues that prevented me from using it.

The author Will Norris got hired by Vidoop the other day to continue working on wp-openid in the context of the diso project. Diso is another thing I’m pretty enthousiastic about. So, things are improving on the openid front.

Tonight, I managed to get version 2.1.9 of wp-openid to install without any issues on my wordpress 2.5.1 blog. I’ve been testing and it seems to at least accept my openid (delegate to myopenid) without issues.

So finally, my blog is openid enabled.

The delegation bit is BTW courtesy of another wordpress plugin: openid delegation. I’ve been using the 0.1 version for more than a year and it just works. Delegation is an openid concept where any website can delegate openid authentication to an external openid provider. This allows you to use a URL you own as your identity and also to switch provider without losing control of your openid url.

links for 2007-07-19