Test driving the Chrome

Google launched ‘Chrome’ - the google browser - and like everything else that is Google, I had to test drive the shinny new chrome the very first day it was available.
First impressions :
Its fast, its clean - its everybit Google!
- No wastage of expensive browser space with a bar on top
- Tabs are just clean and works like magic (unlike IE7).
- Dragging a tab outside opens a new window
- Each tab is a process in itself so you can kill something that hangs up without affecting other tabs (i.e. if you can figure out the bad one from the list of chrome.exe)
-
Things that I didn’t like so much :
- Bookmarks disappear when you open a website on a tab, to access them you have to open a new tab (an extra click)
- No adons
- CPU usage (see below)
- Different processes for each tab is a neat feature, but no id for the right tab to kill, its all “chrome.exe”.
So the big question is - DO I SWITCH FROM FIREFOX or OPERA or FLOCK or MAXTHON, or SAFARI, or even IE7?
Firefox had issues with memory usage, so lets compare that. I ran Chrome, Firefox and IE7 with 4 active websites and an empty tab - here is what we see
While the memory usage isn’t bad, its not too good either. Alarming thing is the CPU usage. I don’t know if I would sacrifice 50% of my cpu usage towards a better browsing experience - when Firefox isn’t really doing a bad job at that and besides I will miss stumbling.
Surely Chrome is my default browser at the moment, lets see how long it retains the position.
September 3rd, 2008 at 11:18 am
Nice review!
As for the bookmarks getting lost you can enable the bookmarks bar to stay on each Chrome tab (Ctrl+B) after sacrificing some browser real estate at the top :)
September 17th, 2008 at 9:37 pm
[…] 2800+ processor and 704 MB of free RAM could not handle the resources that Chrome demanded. As reviewed here Chrome did show an unusual high usage of CPU […]