Google Chrome’s chrome is on the inside

There’s been a bunch of speculation as to just why Google has taken on the browser market with Chrome.  Everybody has a good idea as to why.  Now it is my turn.  And while I’m at it, I want to give a quick review of the features of Chrome and why they might be important.  We don’t get a new browser to play with every day of the week, and this one is different.

Okay, so what is Chrome all about?  Why?

My take is this:  The important features are not in the UI.  Chrome usually refers to pretty UI stuff that isn’t important.  Google’s being ironic here.  Chrome looks ok but is nothing startling or beautiful.   It is low key.  Few menus, calm UI features.  As if the served page matters more than the browser.  Yup.

Basically, Chrome is the first browser that is designed from the ground up to serve web applications fast and seamlessly.  Engineering-led Google has built something to serve Gmail, Google reader, Gears, and other web apps without getting in the way.  In fact, accelerating these applications and all other web applications to make them snappy.

Why?

Beacuse Google’s web app developers have been telling the bosses that what they need is speed, proper memory allocation, decent security and proper multitasking to deliver web apps that really work.  They’ve got a long way with the existing toyish javascript implementations but the limits are clear.  All the other browsers developments were off in user chrome land.  Adding more features and menus and gradually getting faster javascript execution but not quickly enough to keep new applications coming forwards.  

And once you’ve got a good, fast, secure engine in the browser, then you can implement all the chrome you like in javascript in the browser, not in the menus and in the browser executable.  Hooray.

Strategy:  Raising the Bar and Elevating Best Practice

My take on Google’s strategy is to elevate best practice in all browsers so web apps can succeed. That’s why all the components are open source.  We all win (and Google wins more) if we have quick, secure browsers.  So changing the game, raising the bar, and setting a new technical standard for browser best practice is the way to do this.  Packaging it all up in a browser shows it off and gets the early-adopters along for the ride, but I’d guess that Google can handle having the V8 javascript engine and other features show up in Mozilla and elsewhere.

Oh, and it has to nicely unnerve Microsoft.  Always a good thing.

Chrome is fast and tidy and usable, and that’s using it on a Mac using Parallels to run it under Windows XP.  Can’t wait to see a native OS X version. It ought to fly.  Best feature for me, apart from the Internals, is the ability to turn any web app into a single-window application.  We’ve been messing with this in OS X a bit and it is a nice idea, but Chrome makes it easy.

Neat little browser.  But don’t forget the real chrome is on the inside.