Google Chrome dead last
In fact, when running the benchmark, Chrome and its new Crankshaft engine are slower than all the other major browsers. And the fastest browser, in the estimation of Crockford, isn't Firefox or Opera.
It's Internet Explorer 10, which is currently available as a preview.
"JSLint is a code quality tool, and is itself the product of a code quality tool."
His results puts Internet Explorer 10 at the top of the list and Chrome at the very bottom, below Internet Explorer 9. Firefox is the second fastest, just ahead of Safari:
Crockford admits that he expected Chrome to top the list. "My guess is that they overspecialized for specific styles of programming, and that Chrome was tripped up by a real program. There are some very smart people at Google, and I would expect them to rectify this."
Crankshaft uses "adaptive compilation", identifying important or "hot" code and working to optimize that code. In addition to a base compiler, it includes a runtime profile that identifies hot code, and an optimizing compiler that recompiles the hot code to offer such optimizations as loop-invariant code motion, linear-scan register allocation, and inlining. Google also provides "deoptimization support", identifying cases where the optimizing compiler has promised too much optimization. In this case, the engine falls back to the base compiler.
But neither can match IE10. At least in the estimation of Douglas Crockford, a third-party with an appropriately impressive CV. ®
consider the article?
Crockford wasn't involved in the original MS co-authored paper, he merely took its findings regarding benchmarking and used his own js application as a benchmark. I'm involved in a couple of projects which are pretty js heavy and like you generally find that Chrome is markedly faster, closely followed by FF. Crockford's results are interesting with regard to IE10 because it has only just been released as a platform preview. It will be interesting to see how it shapes up at full release - all good from my point of view, healthy competition driving the technology forward.
Crockford's real-world vs. the real-real-world
Let me cut out Mr. Crockford's bias against DOM from this quote, and get it to the part that matters:
He goes on to say:
"My guess is that they overspecialized for specific styles of programming, and that Chrome was tripped up by a real program. There are some very smart people at Google, and I would expect them to rectify this."
Yes, probably "overspecialized" for more DOM intensive styles. You know, like most of the JS that will be encountered in the real-real-world (as opposed to the "real-world" where code analyzers are the majority of the code we run *boggle*).
As impressive as Mr. Crockford's CV may be, he has still missed the forest for the trees. He has created (and I propose we call this) "Yet Another Worthless Browser Benchmark" because of his particular gripes with DOM.
Well there's your problem!
I don't buy it.