2 ms·
I've actually written about JavaScript benchmark quality before: http://ejohn.org/blog/javascript-benchmark-quality/ http://ejohn.org/blog/javascript-benchmark-
by jeresig 18y ago
I've actually written about JavaScript benchmark quality before:
http://ejohn.org/blog/javascript-benchmark-quality/ http://ejohn.org/blog/javascript-benchmark-quality/
(I've since re-written Dromaeo - and the current version that's live is taking in to account all the problems that I outlined in this post.)
I think layout would be more of a performance target if there was a reliable way to test it across platforms - or even on a single platform (especially so from JavaScript). That's definitely something that I'd like to shoot for, though - it would be hugely helpful to developers.
- jwilliams 18y agoThanks for the link. I guess my thinking was -- I hear a lot of anecdotal discussion about the FireFox codebase and how it needs to be re-engineered, etc, etc (ie. WebKit is tidier and so forth). If the performance war is elsewhere, does that remain a factor? i.e. Assuming the above is actually true, does the codebase have legs as the performance war is elsewhere?
- jeresig 18y agoI think that the Firefox codebase is a lot of things. It's been around for a while, for sure. There's cruft - definitely. It's also being actively stripped of its cruft and being actively improved. I think a lot of people are coming to discover just how much 'oompf' the Firefox codebase has. For example, all of these huge JavaScript performance improvements (TraceMonkey) are a layer of additions on top of the existing JavaScript engine (SpiderMonkey). So yeah, there's some really smart people at Mozilla who are making the code base quite fast - just as there are at Apple, Opera, and Google. It's a great time to be a web developers - this performance battle is just awesome on so many levels.