Linked by Thom Holwerda on Thu 23rd Sep 2010 21:36 UTC, submitted by google_ninja
Permalink for comment 442411
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 06/19/13 23:02 UTC, submitted by M.Onty
Linked by Thom Holwerda on 06/19/13 22:28 UTC
Linked by Thom Holwerda on 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
More News »
Sponsored Links



Member since:
2005-09-10
Take that with a grain of salt, especially since the Firefox guys publish benchmarks comparing their latest code with code released months ago. One has to wonder why... Don't assume - like FF devs do -- that the Chrome devs collectively went on a holiday after the 6.xxx release! Besides, why would I trust a benchmark released by Mozilla itself using their own benchmarking tools over something like peacekeeper, that seems to simulate real world scenarios (social networking, logins, encrypting connections, graphics commonly or not so commonly encountered on webpages, etc.). As it stands now, their new javascript engine must beat the one in FF 3.6 by 250% to become competitive against current stable release of Chrome.