zlacker

I've read that a number of times now, but I have trouble matching it to my perceptions. Can you point to a specific website where you notice that slowness and then describe what action is slower? (Initial load, clicking stuff, scrolling, etc.)

Just as an example, loading jslinux.org for me in Firefox is about twice as fast than in Chrome. That might be a special case of course, because it is a very special type of workload that probably is not common on other websites. But I would love to see concrete examples of the opposite.

>>stkdum+(OP)
Put 10,000 or so event handlers with their own DOM updates on a page. Chrome will run it smoothly (taking up a huge amount of RAM in the process), Firefox won't.

>>crooke+Q3
What is the definition of huge amount of RAM? How does Chrome perform when it's RAM constricted? Are we blaming Firefox for poorly designed websites?

It feels like this is a straw man constructed to bash Firefox, rather than a real world scenario.

>>stkdum+(OP)
WebGL / Canvas heavy sites are typically significantly slower in Firefox compared to Chrome. Google Maps is a pretty good example of this.

>>cptski+I5
Extremely poorly-optimized websites are far more common these days than even mildly performant ones.

>>crooke+b7
Do you have an example of one with 10,000 event handlers? If the case where Firefox falls isn't real it doesn't matter that other sites suck (not arguing that fact).

>>000000+u6
To be fair though, Google maps is an awful beast on any browser compared to older versions.

>>crooke+Q3
That's not a specific site though.