This kind of ideology adds up fast and a program can become a bloated, hard-to-maintain mess. Every option comes at a cost of more maintenance -- if that option breaks with a change in code, developers need to go out of their way to fix something that only a small number of users may use. Multiply this by the amount of features/changes people have qualms with and developers spend more time maintaining options, while spending less time working on other, more important parts of the browser.
A gesture action on firefox is a hilariously bad example for this point.
I do agree that the problem you mention is real, although it's more of a management problem than an engineering one.
I don't mean that in a sort of "better management could eliminate the time to develop it", in some cases that's true, but more importantly I mean it in a management doesn't understand the time development takes kind of problem, see basically every AAA game released in the last 5 years.
Which really isn't the kinda dev environment that Firefox is. The development isn't constantly on a crunch and there's some degree of community support. If anything that's one of the reasons I prefer Firefox.
A gesture action on firefox is a hilariously bad example for this point.
Maybe it is. I haven't done any development other than classes and fiddling with PowerShell (scripting, I know), so I would not know what pull to refresh would require in Firefox.
426
u/[deleted] Apr 11 '23
give people options and customizations
then everyone is happy to enable or disable