Are you arguing that Firefox is not even "good," or just not perfect?

(I use Firefox on a Mac all day and the only kind of "resource hunger" I've observed can be pinned to the web pages that it's running.)

I’ll extend the quote a bit more:

> make it good. For many of us it isn’t

I’m saying Firefox isn’t good enough for many of us (mostly various subsets of macOS users).

As for resource hunger, in my case I see it in headless mode (it always turns the fans on), but every point in that list apart from (lack of) AppleScript support was lifted from other complaints I’ve seen in similar HN threads, not my experience.

Most of those problems I could live with in the name of supporting Firefox, but not the lack of AppleScript support. That seems to be the case for many of the aforementioned macOS users: we want to like Firefox, but theres a detail it screws up so bad for our needs, it becomes unusable as a daily browser.

The vast majority of computer users are still not using MacOS and those people can also do some good by using Firefox even if you can't.

When it comes to "slow" and "resource hungry" the Firefox devteam is very responsive to bugs. I've had approaching a dozen performance issues I personally reported get fixed.

Both of our points can be true and the same time, and I believe they are.

Sites render badly (names colors and fonts look wrong on Firefox but look the same on Edge Chrome and Safari (macOS))

It hangs multiple times a day

Some heavy JS sites are much slower in FF than Chromium

It takes dev tools minutes to become responsive on the site I work on, while in Chromium they load up very quickly.

In other words: Blink, Blink, and WebKit (of which Blink is a fork) look the same. This is why people talk about supporting Firefox to avoid a monoculture.

Chrome also has regular zero-days.