PokedexNFF VS firefox-performance-dashboards

The goal of a JavaScript engine’s code parsing and execution process is to generate the most optimized code in the shortest possible time. Bottom line, the evolution of these engines parallels our quest to evolve the web and mobile environments to make them as performant as possible. To track this evolution, you can see how various engines perform in benchmarking graphs such as those produced on arewefastyet.com.

> Have you actually seen Firefox source code?

Yes.

> It's horrible; not one bit surprising that Chromium won!

Nope. It's just old (maybe older than you, even, IDK). It's Netscape, actually. It's very commendable that the codebase we're talking about has been successfully evolved up to that point [0].

[0]: https://arewefastyet.com

https://arewefastyet.com/ has various comparisons between Firefox and Chrome, the script oriented ones are basically Spidermonkey vs V8

> This will be the end of an era where users still had control.

Google land never had it. The land with choices is called Firefox, and yet people still believe that it's a slow, bloated, supports-nothing browser.

Google does the advertisement part well, it seems.

For facts: see https://arewefastyet.com

> Show me these pages that Firefox doesn't render well.

I'm not doing homework for you. Lots of pages don't render well in Firefox, it's a well known issue which is why it comes up in every thread about Firefox.

> Show me pages that tank Firefox performance.

Firefox in general performs poorly. Again, known long-term ongoing issue. Look at this thread where almost every top-level comment is sceptical that Firefox is even close to Chrome in performance: https://news.ycombinator.com/item?id=36770883

You can find ongoing performance benchmarks between Chrome and Firefox here, and it's not flattering for FF: https://arewefastyet.com

> How many of them will have -webkit-* and other engine-exclusive markup/CSS?

I don't care, at all. It's not my job, as a user, to debug performance problems.

> Firefox updates every 6 weeks, just like Chrome.

Ok? I didn't say anything about update cadence.

The link is terrible. Maybe the article should link to https://arewefastyet.com or maybe the Speedometer selection at https://arewefastyet.com/win10/benchmarks/raptor-desktop-spe...

Well I would wager a guess it's due to consistency. The full site includes a bunch of different benchmarks, with a lot of them having the y axis as execution time in milliseconds. Meaning, lower is better. They probably just wanted to keep that consistency even with tests that use scores. Definitely a bit misleading without the full context. The full site is arewefastyet.com

They do... They just don't have the resources Google does. If you see https://arewefastyet.com you can see that Firefox has been steadily improving in speed, and they have actually recently been working to make react faster.