commentary The internet has exploded in a single, joyous, mass-hallucination called Chrome. Apparently it's the fastest browser ever and will solve a myriad of problems from slowness within Google Spreadsheet to possibly creating an acceptable carbon trading scheme.
Immediately my bs detector went off the scale and I decided that I had to test this claim with some solid figures.
The browsers used here are:
- Google Chrome beta
- Firefox nightly build, TraceMonkey branch
- Webkit nightly build
- IE beta 1 (not beta 2, as it is a pain to install/remove beta 1)
- Opera Final 9.52
Chrome sets the score to beat in Google's own tests.
The challengers can't even get close to Chrome, the best being Opera which gets close to halfway.
Below you can see that Chrome truly is quick — however, it is not the order of magnitude that Google claims (unless it is IE).
WebKit is able to best Chrome in a number of SunSpider tests. (Click for complete SunSpider results)
Similarly, Firefox is able to beat Chrome in the regex and some string tests. (Click for complete SunSpider results)
Opera is able to get very close to Chrome over a range of tests, but is unable to prevent always being the bridesmaid. (Click for complete SunSpider results)
The significant speed-ups we have seen from the browser vendors will only continue, and Google has raised the bar far higher than it was yesterday.
But it's not to high that no one else has a chance to catch up. Google has landed the opening blow and has had the element of surprise, it's time for the SquirrelFish's and TraceMonkey's of the world to bite back.
And it can't go without saying that Chrome fails the Acid3 test, which its WebKit brethren can pass.
The development version of Webkit has been able to pass the Acid3 test, but it fails in Chrome.
Some would say that it is a long way from software engineering to journalism, others would correctly argue that it is a mere 10 metres according to the floor plan.During his first five years with CBS Interactive, Chris started his journalistic adventure in 2006 as the Editor of Builder AU after originally joining the company as a programmer.Leaving CBS Interactive in 2010 to follow his deep desire to study the snowdrifts and culinary delights of Canada, Chris based himself in Vancouver and paid for his new snowboarding and poutine cravings as a programmer for a lifestyle gaming startup.Chris returns to CBS in 2011 as the Editor of TechRepublic Australia determined to meld together his programming and journalistic tendencies once and for all.In his free time, Chris is often seen yelling at different operating systems for their own unique failures, avoiding the dreaded tech support calls from relatives, and conducting extensive studies of internets — he claims he once read an entire one.