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...
We need modular browsers. It is hard for Mozilla to keep the track to the W3C and all the nonstandard stuff that Google, Microsoft and Apple add to their browsers. If those elements were modules, it would be easier for people to collaborate and for Google and Microsoft to be obligated to add support for other browsers.
You’re talking about a modular rendering engine, which is a different thing than what I’m talking about. I’m talking about stripping down the UI until it resembles XUL Runner, then adding the functionality back as extensions.
You’re not wrong that it’s important for the engine’s code to be organized well for developers’ benefit (and ideally for the engine as a whole to be self-contained – it’d be great if Gecko were as easily-embeddable as Blink), but I’m not so sure that users need to be able to add or remove pieces of it in a way similar to what I’m talking about for UI features.
More concretely:
I think Firefox should ship by default with all the functionality it currently has, plus uBlock Origin and some other things. But I want it to be designed such that if you went into the extensions manager and disabled everything, things like tab support, bookmarks, history, and maybe even the address bar and back button would be gone. It would still be capable of fully rendering a web page, though.
If they do that, normies will start yelling that Firefox has removed their beloved features and will immediately download Chrome. I have a strong suspicion that a majority of people don’t use extensions at all.
Okay. Replace core features as extensions. Kind of like the suckless philosophy.
While it’s a good idea, I think extensions are purposefully made weaker, that is, they don’t/can’t have the same capabilities of core features. It will require a huge rework which I just don’t see happening.
We need modular browsers. It is hard for Mozilla to keep the track to the W3C and all the nonstandard stuff that Google, Microsoft and Apple add to their browsers. If those elements were modules, it would be easier for people to collaborate and for Google and Microsoft to be obligated to add support for other browsers.
You’re talking about a modular rendering engine, which is a different thing than what I’m talking about. I’m talking about stripping down the UI until it resembles XUL Runner, then adding the functionality back as extensions.
You’re not wrong that it’s important for the engine’s code to be organized well for developers’ benefit (and ideally for the engine as a whole to be self-contained – it’d be great if Gecko were as easily-embeddable as Blink), but I’m not so sure that users need to be able to add or remove pieces of it in a way similar to what I’m talking about for UI features.
More concretely:
I think Firefox should ship by default with all the functionality it currently has, plus uBlock Origin and some other things. But I want it to be designed such that if you went into the extensions manager and disabled everything, things like tab support, bookmarks, history, and maybe even the address bar and back button would be gone. It would still be capable of fully rendering a web page, though.
If they do that, normies will start yelling that Firefox has removed their beloved features and will immediately download Chrome. I have a strong suspicion that a majority of people don’t use extensions at all.
Did you miss this part of my previous comment?
Okay. Replace core features as extensions. Kind of like the suckless philosophy.
While it’s a good idea, I think extensions are purposefully made weaker, that is, they don’t/can’t have the same capabilities of core features. It will require a huge rework which I just don’t see happening.