Edit: not to mention that you can configure the number of webrender processes Firefox uses to render web pages. If you have a fast enough processor, just set it to one or two and call it a day.
Chrome uses a more complicated algorithm based on the source domain and the tab "dependency" tree. You have pretty much zero control over this.
I don’t heavily use tabs like 50+ but people who do say Firefox uses less RAM.
Either way it’s fast enough now for me not to have any performance complaints.
They've been putting out blog posts over the last 2 years specifically talking about the performance fixes they've put in.
Firefox themselves have admitted it's not FUD. They acknowledged it was a real problem.
It is pretty fast now, but a few years ago (at most 4), it was bloody awful.
Good job you don't work in user experience design, then, because how things feel to people is a huge part of that. If software feels bad to use, people won't use it, simple as that.
No amount of haughtiness from your high horse will change that.