See: http://code.google.com/p/v8/
This is Googles new Javascript engine.
And running the tests their engine is really fast: http://code.google.com/apis/v8/run.html
See the results for Googles Chrome:
Firefox 3.0:
And last but very least Internet Explorer 7.0:
IE7 even came with this warning while running this script:
So Google has a point about rebuilding the lot.
See the strikeback of Firefox:
http://arstechnica.com/journals/linux.ars/2008/09/03/new-firefox-javascript-engine-is-faster-than-chromes-v8
Although Chrome's performance beats the current stable version of Firefox, benchmarks show that Mozilla's next-generation JavaScript engine actually outperforms V8.
And: http://webwereld.nl/articles/52431/firefox-3-1-maakt-javascript-tot-40-keer-sneller.html
Still there is the behaviour of the browser tab being stuck completely, see:
http://www.flog.co.nz/journal/welcome-to-the-web-chrome/
Try http://labs.flog.co.nz/raytracer/ with the best quality (1x1) in Chrome:
While this processing is eating one of my cores, it can still be stopped.
And Chrome will survive painlessly!
Only one tab is stopped as each tab runs in a separate process.
The competition Googles Chrome causes is good for Web 2.0 and the extensive use of AJAX to offer a rich client.
So next will be Firefox3.1 (https://wiki.mozilla.org/Firefox3.1) and IE8.0 (http://www.microsoft.com/windows/internet-explorer/beta/readiness/)
No comments:
Post a Comment