User css and js, which were once first class are now very hidden and require messing with about:config. There's no way to prevent tabs from being on top. Many extensions are no longer possible Post-Quantum. And I do think switching to WevExtensions was the right move, but they've been slow in adding capabilities to make some extensions work as well as they did before. Removing compact mode (they added it back but behind an about:config flag). They removed SSB with no plans to ever add it back. True SSB didn't fully work, but I had high hopes that it could let me run web apps in a way that felt more native.
And part of my frustration is with the response. The reason for removing things is often "no one is using it." But then when people who show up saying they use it, and it is important to them, Mozilla generally either outright ignores them, or dismisses those opinions as invalid.
Now after this you may want to refer back to the article. I have seen various pieces and rants like this article that complain about this but none of them offer any more reliable sources of information. The article makes an unverifiable claim of "Almost everyone hated the changes" and unfortunately those type of claims seem to be extremely common instead of presenting some data. That's not enough to change anyone's course.
But in the end, I don't know what you mean by "systematically removed" in that way, frequent addition and removal of various features is completely normal for a large project. And technically only the setting was removed -- you can still customize all that but you'll have to modify the browser itself. No they probably won't add back in the setting but as I explained above, those have a cost, and when the cost-benefit analysis doesn't play out the right way, it doesn't make sense to blame an organization for cutting it.
You are suggesting that I replace a simple configuration change with familiarizing myself with a very complicated code base, creating a patch, and running a build that on my machine takes multiple hours, then repeat the process for every update? Yeah, I have no idea why more people don't do that.
> I don't know what you mean by "systematically removed" in that way, frequent addition and removal of various features is completely normal for a large project.
Sure. But from my perspective at least, the customisability is decreasing, more features are being removed than added. It used to be that Firefox was a browser built for power users, but it is becoming less so. That was one of it's major advantages over chrome.
I understand the cost of maintaining features, and the tradeoffs involved. The Firefox teams priorities are different than mine, and I understand that. For example, there are many features I would have rather seen worked on rather than redesigning the UI (and I do actually like a lot of the proton design). But I can accept that they have different priorities. But they are also bleeding users, so something is clearly not working for them. And maybe, as the OP suggests it is because of changes that anger a minority of their users. At some point, the union of many minorities becomes a majority.
Then why do you keep being so?
But, I bet you'll refuse to understand this too, and continue your bot-like repetition of non-answers. (Hint: Don't bother; nobody is buying.)
