5 ms·
The big one for me is that Chrome's JavaScript engine is much faster than Mozilla's. I'm not sure why, but it makes a noticible difference. I use this to my ad
by julianlam 4y ago
The big one for me is that Chrome's JavaScript engine is much faster than Mozilla's. I'm not sure why, but it makes a noticible difference.
I use this to my advantage by using FF as my daily driver. I believe that if my site is fast on Firefox, then it's damn near fast enough for everyone.
- drathier 4y agoLots of web devs only testing in chromium browsers, perhaps?
- irrational 4y agoWhat we do at my company is I only test in Firefox, another developer only uses Chrome, a third only uses edge and QA tests on Safari.
- robin_reala 4y agoI ran into an interesting situation where I was building a Conway implementation and getting 60fps in Firefox / 10fps in Chrome. Turned out that Chrome had absolutely horrible performance with attempts to access out-of-bounds array indexes, where Firefox had some early fail fasts in place. So anecdata, but I wouldn’t rely on Chrome automatically working well if Firefox does.