A Week of Chrome
Tuesday, September 9th, 2008So, I’ve used Google Chrome for an entire week now.
It’s nice. It’s clean, simple and fast. The UI is unobtrusive. It blends seamlessly into the look and feel of Google Applications (Reader, Mail, Calendar, Docs, Spreadsheets, Groups) but as a browser, it felt a little wrong. Things weren’t quite right. No home button unless I turn it on? Search in the address bar, powerful, but a bit of a mind twist to remember that’s how it works. No firefox style URL keywords. Bookmarks very marginalised (have to turn on the “bit horrible” bookmarks bar to get at them).
Then I read this:
Now along comes Google, carrying two nuclear missiles: Android and Chrome. Both are immediate problems for Microsoft. Let me be absolutely clear: Chrome is not a Web browser, it’s an application runtime. Chrome is really Google Gears with a browser facade. Sure, Chrome is based on Webkit and has browser legacy, but the product’s core capabilities—and Google’s objectives for them—is running Web applications. Chrome is a development platform, but in the cloud instead of on the PC. Way I see it, Chrome is the Google OS.
Which really put it into context for me. Google Chrome’s Application Shortcuts feature is great. Gmail runs really nicely in Chrome with that shortcut option. But as a day to day browser? It just doesn’t work for me.
It’s not just the lack of adblock. Or just the lack of del.icio.us integration. Or the lack of a home button by default. A separate search. Greasemonkey. Cookiesafe. NoScript. Developer Toolbar. Firebug. It’s the fact it’s streamlined for a purpose other than surfing.
It is a web based operating system.
Perhaps to move it to be more a browser, will make it fail as a web based operating system. But, to keep it as a web based operating system might fail it as a browser. Only time will tell.
But for now I at least return to Firefox, hoping some of the Chrome innovations will come to Firefox soon.
Popularity: 40% [?]


