Linked by Thom Holwerda on Thu 23rd Sep 2010 21:36 UTC, submitted by google_ninja
Permalink for comment 442424
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 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2005-10-13
You have to remember that the faster a browser gets, the harder it is to keep improving. V8 is getting closer and closer to running at native speed, and every millisecond they improve is an accomplishment. Meanwhile, Firefox is adding a whole new compiler they didn't have before, so massive improvements are to be expected. They're also cherry-picking code from both V8 and Webkit to improve their performance where it makes sense. For example, they ported over YARR (Webkit's regular expression engine) for FF4.
That said, there's no way FF4 is going to be faster than Chrome when it comes out. It should be about on par with Webkit, which is plenty competitive. V8 will maintain a lead.
Edited 2010-09-24 07:43 UTC