If users have 200+ tabs open and are experiencing slowness, I'd suggest that altering the users behavior isn't a fix. To me that's pure failure from Product designers to realize that "they shouldn't do that" doesn't cut it. Fix it.

Spending time and money on solving these issues isn't going to generate new revenue. I find it hard to believe engineers wouldn't want to try fix performance issues. I find it easy to believe leadership at Mozilla would find it unimportant.

edit: clarification

I think you are wrong there. As a product designer one never caters to edge-cases. Besides having 200+ tabs open is very impractical, the way Chrome minifies all the tabs instead of making them slidable is just one prime example where the designers chose not to cater to the extreme. Even with a tab-behaviour like Firefox's it is a very unmanageable situation. Also note that one might encounter a tradeoff in system-design where you could choose a very memory/resource-efficient design over a very performant one. You cannot always get both.

Unfortunately, because Google is "In" just because it delivers mind-numbing ease via Youtube etc., this very vocal minority, claiming technical expertise scew impressions for the general population.

Similar to absolute views like :They do not care... I think they care, not about the particular problem, but the product and how it meets the requirements of a general audience swiftly and reliable. So the problem crossed their desk, they triaged it and closed it because it is an extreme use case which will not meet general requirements.

The same goes for all the multitudinous problems in that area.

I wasn't necessarily meaning the visual experience of having tab inception open, more along the lines of people feel that FF is slow. The 200+ comment was based around that there were quantifiers - it's the users fault for having slow software. "You're just doing it wrong".

From a Product perspective Chrome is the better product. I want to believe that Mozilla is capable of making FF the better product. Maybe it all boils down to Youtube and Facebook and in actuality it's impossible and they can't actually have a better browser. I don't really believe that. I do believe that Mozilla isn't on a trajectory to make that happen.

Luckily what you and I believe is irrelevant, unless we try to convince the masses by screaming at them long enough.

I wasn't referring to the tabs either, just as an example of people doing it wrong. No one stops them, but in the old days natural selection took care of it. These days people think, because they have a misconception, they have a right to an opinion which a misconception is not. This is known as "The terror of the masses". Desinformation and Fanboydoom(we against them) is based on that.

Yes FF was slow some 5/7 years ago, but speed up quite a lot. See here https://arewefastyet.com/win10/overview?numDays=60 . You can, of course, choose the Benchmark proving your point, or look at the bigger, quite different, picture. And just because 200+ people write the same comment in spirit does not make it true (see benchmark-site) . Also, as I have pointed out elsewhere in this thread, it is not just about speed. I agree that a site should not be agonizingly slow to work with, but that is not the case with FF (see benchmark). As far as the reference to the trajectory is concerned, it is not s.th. that securely predicts outcome. You never know what the future holds. Just think of the situation of MS or Amazone some 10-15 years ago. Besides Youtube and Facebook have nothing to do with the browser; also note that Alphabet purposefully sabotaged their own website so that it performed bad or even breaks on a non-Chrome browser. https://www.zdnet.com/article/former-mozilla-exec-google-has...

I would also like to remind the reader and you that I never said that the fault is with the user, I merely stated that you cannot demand a product owner, ANY product owner, to cater to ALL and EVERY extreme edge-case.

But since this debate of ours, I fear so, because you tried to warp above said statement of mine, is in danger of devolving into a fan-boy flame thread, let me close this with a quote I read in a facility of a philosphical faculty, in hopes that it gets people thinking before they regurgitate other people's/trolls/campainers opinion/misconception unreflected: "People, eat feces, for a 1000 flies cannot lie."

>As a product designer one never caters to edge-cases.

The edges are where some of the most faithful users live. But you're right, it's becoming more and more clear, over various updates and certainly with the recent news, that Mozilla thinks they could do without the trouble and their PMs act accordingly.

Whether it's an issue that only one in a hundred users has to deal with, or an issue that every user has to deal with once in hundred of their actions in a browser session, an edge case is just an edge case.

I've been using Linux for a lot longer and on variety of hardware. I don't have this problem on my desktop, but the laptop and the trackpad are rather fresh, so maybe somewhere there's a bug or something. For some reason whenever there's a problem it's always Firefox, and rarely if ever Chrome. Example of another problem I had recently - websites like whathifi, tomsguide and a bunch of others were using 100% of one CPU core on Firefox, no problem on Chrome.