I don't care about synthetic benchmarks. And this one essentially only tracks js (and webasm) performance, not the overall performance, not even just web perfor

I don't care about synthetic benchmarks. And this one essentially only tracks js (and webasm) performance, not the overall performance, not even just web performance as this would entail DOM manipulation, layouting and rendering, which this thing doesn't really do. It may have some meaning when all you do every day is use websites that are mostly compute instead of mostly idle. Only very few users will do that, while most users will use mostly idle websites, me included, and then it doesn't really matter if Firefox or Chrome can execute a piece of code 5ms faster than the other. It mattered back in the sunspider days, when js perf was really bad, and Firefox 3 outperformed the IE of the time by a factor of something like 20. But we're at a state right now of highly optimized js engines, so a benchmark difference saying V8 is marginally faster than Spidermonkey isn't really meaningful over all to me and how I am using the browser. I care a lot more about "lived" performance, and that's where Firefox performs better for me. YMMV. E.g. I regularly have noticeable stalls in Chrome e.g. when doing page navigation or just switching already loaded tabs. Nothing massive, but I do not have the same thing in Firefox. I didn't mean to imply there is a real major difference. Firefox is just a little better. But anyway, since you asked: I just very unscientificially ran the benchmark in Firefox and Chrome just now, wasn't motivated enough to make it entirely fair by shutting down other processes which may "steal" CPU time, etc, and the grand result was... Chrome's score was 1.103x the score of Firefox[0]. Chrome is faster in raw js perf, but at the same time, this is still misleading, I would say, considering the context I provided. [0] I know that on more high-end systems than this shitty laptop I am writing on right now, e.g. systems like my actual desktop, the difference might be larger[1], but even then it still holds true for me that js perf differences are mostly noise in my daily use, and Firefox edges out Chrome in other areas that I actually notice. [1] e.g. mozilla's own arewefastyet have Chrome at about 1.4x as fast in JetStream2, and they aren't running this on a shitty laptop like mine. V8 is a terrific js engine, I am not denying that. But js perf is only a small part of the entire picture. https://arewefastyet.com/win10/benchmarks/raptor-desktop-jetstream2?numDays=7 https://arewefastyet.com/win10/benchmarks/raptor-desktop-jet...