Browser Wars: WebKit Regains Lead Over Chrome
When Google released Chrome just a few weeks ago, we praised it for its innovative user interface and the speed of its JavaScript rendering engine, which blew away the competition. Now, however, WebKit, the open-source project that forms the basis of both Chrome and Apple's Safari browser, has released the latest version of its own JavaScript engine, SquirrelFish Extreme. In our benchmarks, this new engine turned out to be significantly faster than Google's V8 JavaScript engine.
While Chrome is based on WebKit, Google replaced the SquirrelFish JavaScript engine in it with V8, a brand new engine, which, according to Google, makes better use of modern, multi-core processors than its predecessors.
Benchmarks
We used the SunSpider benchmark to test the latest version of WebKit against Google's Chrome. The results are quite impressive. WebKit with SquirrelFish Extreme finished the benchmark in 1235ms while Chrome needed 1598ms. The latest production version of FireFox took 3424ms to complete the benchmark. We were not able to test FireFox with TraceMonkey enabled (running the benchmark crashed the browser), but judging from these results, it is clearly a lot slower than both ScquirrelFish Extreme and Chrome.
We also ran the Mozilla affiliated Dromaeo benchmark, which takes a more holistic approach and does not just look at the JavaScript engine. Here, too, SquirrelFish Extreme outperformed Chrome's V8 (4522ms vs. 5206ms).
In case you want to try these benchmarks for yourself, you can download the latest version of WebKit with SquirrelFish Extreme from here.
Competition at Work
When Google launched Chrome, it emphasized that it wanted to bring more competition into this market and to push the development of faster and better browsers. The fact that both the Mozilla and WebKit teams are working so hard to beat Google definitely proves that there is still a lot of room for improvement and that Google's plan is working.
Share
Comments
Subscribe to comments for this post OR Subscribe to comments for all ReadWriteWeb posts
And when Microsoft releases IE8 sometime in the next decade it'll look like a Ford model T compared to these beauties.
What I find interesting is in the recent ReadWriteTalk http://readwritetalk.com/2008/09/08/rww-live-google-chrome/ about Chrome, Aaron from Google said that V8 would be submitted to the webkit project. So will V8 and SquirrelFish Extreme be combined?
I think Gecko could be the big loser here. The Mozilla XUL and plugin architecture have been great but again in the RWT interview Aaron mentioned Greasemonkey coming to Chrome and a new plugin architecture.
What I am confused about is the commercial position of Safari and Chrome?
This is not an example of Chrome driving innovation. Both Mozilla and the Webkit team were already working on their next-gen Javascript engines when Google surprised everyone with the Chrome
But remember that Firefox has a next-gen JS engine still in the works, Tracemonkey, which will be in version 3.1. They should all have somewhat even performance a little while from know, and Firefox will still lead because of it's extensibility.
As the browsers try and out do each other, this is all good news for us the user.
I have never heard of webkit, I was just searching for better browser, thanks for the info.
Please, it's Firefox, not FireFox.