As someone who recently switched to Firefox on Linux partially due to performance.. it is really a toss up. Some sites FF renders faster, others Chrome. Chrome does tend to do a bit better on large javascript heavy 'single-page-app' type sites while Firefox crushes Chrome when displaying large (as in lots of text) pages. The latter made reading documentation impossible, such that I always had to use FF for it.

Plus you get the benefit of Firefox not corrupting its session weekly. Losing all your cookies, tabs and history frequently got super annoying.

Both synthetic and real-world benchmarks show the opposite [0] [1]. My own experience and unresolved performance bugs that I've filed show the same [2].

I want Firefox to be faster and superior to chrome in every way. Ignoring it's problems won't make them go away and definitely won't make them a priority for the devs.

[0] https://blog.macsales.com/46993-rocket-yard-testing-lab-whic...

[1] https://www.phoronix.com/scan.php?page=article&item=firefox-...

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1408699

> Further, it is absolutely not up to par on Linux

I am sitting on Arch here, Firefox Wayland and it's absolutely up to par, in fact Chromium seems less responsive these days. Granted, I have a very tuned, minimalist install, maybe on the likes of Ubuntu it's a different story.

I switched to Firefox about a year ago on Mac, and coming from Chrome I've been totally satisfied. Not that I've run any comparison benchmarks or anything, but it'll load basically anything I want to throw at it, has the right set of extensions to keep me rolling, and the only real performance issue I've noticed with sites is the occasional rendering block waiting on content I have blocked with uMatrix. But that last one's my fault, not Firefox's.

I use a 2017 Macbook Pro in work, on which I use Firefox as my main browser.

I also have Firefox on my Windows 10 gaming machine at home and while I haven't run any performance anaylsis, I can;t tell the difference between the two in terms of speed and responsiveness.

The Mac version has crashed on me a few times though whereas my Windows 10 version hasn't.

Other than the OS they are on the two browser instances are set up exactly the same way.

It’s got great performance on macOS, and I suggest that people try it again.

Firefox still feels non-native on OS X as a result of its reliance on XUL. My main issues are around UI. The menu bar only fully populates once the browser is almost loaded, not when the browser is first opened. The other thing is that UI elements exist in an uncanny valley, where they are not quite native, but not quite foreign.

Camino meant to fix that, but it has moved onto greener pastures.

> "Firefox still feels non-native on OS X..."

As opposed to Chrome? Or Opera, Vivaldi, etc?

Browsers are a class of application whose UI's have been "native" only to themselves for years now.

Didn't they get rid of XUL entirely several releases ago?

See jorvi's comment: https://news.ycombinator.com/item?id=19264960 there are some bugs that drive me back to chrome when I try it