At Mozilla, we work hard to make Firefox the best browser for you. That’s why we're always focused on building a browser that empowers you to choose your own path, that gives you the freedom to explore without worry or compromises. We’re excited to share more about the updates and improvements we ha...
I want fewer built-in features, not more of them. All of these things should be extensions, not built into the browser core.
I mean, I’d be perfectly happy for said extensions and more to be shipped by default – it would be good for Firefox to come “batteries included” even with adblocking and such, and that’s most likely the way I would use it. But I just want it to be modular and removable as a matter of principle.
I remember how monolithic Mozilla SeaMonkey got too top-heavy and forced Mozilla to start over more-or-less from scratch with PhoenixFirebird Firefox, and I want it to stick close to those roots so they don’t have to do it again.
Yeah, me too. I made once a pacman hook that empties the respective folder in /usr on update/install. I have no use for all of them and picture-in-picture is annoying to me.
Btw, i think it’s mentioned somewhere in about:support too?
I want fewer built-in features, not more of them. All of these things should be extensions, not built into the browser core.
I mean, I’d be perfectly happy for said extensions and more to be shipped by default – it would be good for Firefox to come “batteries included” even with adblocking and such, and that’s most likely the way I would use it. But I just want it to be modular and removable as a matter of principle.
I remember how monolithic Mozilla SeaMonkey got too top-heavy and forced Mozilla to start over more-or-less from scratch with
PhoenixFirebirdFirefox, and I want it to stick close to those roots so they don’t have to do it again.They are probably extensions, just like pip, pocket, screenshot upload, languages, search engines, themes, etc.
Shipped by default, handled like extensions internally but not exposed to the user. You see it in the extension*.json files in your profile folder.
In that case, I want them exposed just like user-installed extensions, so it’s more obvious how to get rid of them if you want.
Yeah, me too. I made once a pacman hook that empties the respective folder in /usr on update/install. I have no use for all of them and picture-in-picture is annoying to me.
Btw, i think it’s mentioned somewhere in about:support too?