Good question :) I didn't write the article, maybe ask @lucidchart on Twitter? According to the actual article title though, it seems the main interest was testing FF4 and IE9 against existing browsers, which would explain the absence of dev channel versions of Chrome.
Note that it's an "user drags something in the UI and we measure something" benchmark, so it's potentially suspicious if the things measured are comparable at all in different runs and browsers.
For example, in games, frames per seconds are measured under basic assumption that the game has the mode in which there's no limit the increase of frames per second other than the speed of rendering and that that mode is always identically reproducible.
Are we sure about that here?
And as others noted, they are using the old version of Opera, 10.53 instead of 10.62 which is current.
As an interesting comparison, I just saw that John Resig posted a benchmark of jQuery.css() performance across browsers. It doesn't include IE9, but does include Opera 10.62 and FF 4.0b6 - http://www.flickr.com/photos/jeresig/4999526752/
8 comments
[ 3.2 ms ] story [ 28.6 ms ] threadAs noted in a previous comment, a fair comparison would be to run a proper benchmark--which guarantees similar operating conditions.
JaegerMonkey is in Fx nightly builds at the moment and is supposed to be featured in Fx4b7 (to be released later this month).
For example, in games, frames per seconds are measured under basic assumption that the game has the mode in which there's no limit the increase of frames per second other than the speed of rendering and that that mode is always identically reproducible.
Are we sure about that here?
And as others noted, they are using the old version of Opera, 10.53 instead of 10.62 which is current.