> But Firefox wins, against stereotype, for memory usage and page load speed (more so with ad blockers installed). I'll agree on memory, and that's one of the

> But Firefox wins, against stereotype, for memory usage and page load speed (more so with ad blockers installed). I'll agree on memory, and that's one of the reasons I continue to use Firefox but memory is not speed. It's my impression that Chrome wins on JS execution and DOM manipulation/reflow, which is really what I are about as a developer and (generally) as a user. When you're on a low end machine, these make a big difference. When you're on a machine like most developers have, it really doesn't except in technology demos. The Jaegermonkey and Layers work should help out, but I'm not sure that Firefox will ever catch Chrome. It's a difference in development philosophy. Webkit reverts ANY performance degradation while Mozilla reverts all performance regressions except for new features. I prefer Mozilla's philosophy since the places where this matters is generally a performance vs edge case correctness tradeoff.