google chrome
When I returned from vacation, the first work-related thing in ran into was Google Chrome. Clearly another Google product, I lost interest in it right away. As it turned out to be a browser, it was something I couldn't ignore after all. Since then I fired it up a couple of times, so here's my obligatory 'every blogger needs a post on Google Chrome' write-up.
My main issue with Chrome is pretty clear, and has not so much to do with Google's actual product but with the current browser landscape. When things are finally stabilizing little by little, with the big four being enough trouble as it is, who needs a fifth (possibly) major competitor? The only savior of Chrome was a browsing revolution.
the chrome revolution
Main selling point of Chrome is the V8 javascript engine, rumored to be the fastest in browser land. A title which I guess it held for a whole week. There are already rumours and benchmarks putting Firefox and Safari in the lead again. And even then, while solid javascript performance is a good thing, looking at javascript as the way of the future sounds rather primitive to me.
More impressive is Chrome's threaded tab approach. Each tab has it's own thread, allowing it to crash and perform separately from the browser itself. A nifty feature, which I guess will be quickly adapted by others. But at least for a while, Chrome will have the edge there.
As I skimmed down the list of new features, I quickly ran into mentions of a "new tab system" (placing the tabs on top of the window) and similar features. In my eyes, simple bollocks to cover up the lack of more interesting things to mention. So basically, a fast javascript engine and threaded tabs is all Chrome has to offer us for now.
the chrome deception
Even though the browser is rumored to be pretty quick, I believe it feels a noticeable amount slower than other browser. Especially the lack of action and progress after clicking a link or browsing back is hugely annoying, creating a pretty laggy feel while surfing around. In comparison to other browsers, it might be quicker (in actual time), but the feel of the thing is pretty slow and convoluted.
As a web developer, there's also the question of how Chrome will be influencing our daily work. The good news is that Chrome's using a version of the WebKit engine (same one Safari is using), what worries me though is whether Safari and Chrome will continue to use the same version of WebKit. If not, this will mean more work for us web developers, having an extra browser to worry about (as if four wasn't enough already).
the chrome problem
The real problem with Chrome is that I really don't see the use of it. IE is there for your average Windows user, Safari helps the average Mac user, if you expect more from your browser you pick between the leaner Opera or the bulkier Firefox. But I honestly can't see why anyone would be picking Chrome. Not advanced users, nor average users. It has very little that separates it from other browser, nothing that will give it an edge for longer than a year, and it's severely lacking in other areas.
For me, Chrome is very much an unwanted and unneeded addition to the browser world. Maybe Google could've blogged about separate tab threads and could've invested in other people's javascript engines. I can only hope Chrome dies a fast and early death. If not, it'll be another browser on the list that needs to be checked but will never be used.