The issue with this is that the more deeply customisable a fork would be the further it would stray from upstream (and by extension the more dev resources it wo

The issue with this is that the more deeply customisable a fork would be the further it would stray from upstream (and by extension the more dev resources it would require to maintain). > I keep hearing the Firefox codebase isn't very modular and makes it hard to pursue such a project, and I don't doubt it. But aren't there enough of "us" out there to make a concerted effort? There's been plenty of people making such an effort, but yeah it does appear to be "hard". If you're interested in following previous work, some relevant links: - Overview of Myk Melez's efforts in this space https://mykzilla.org/2017/03/08/positron-discontinued/ https://mykzilla.org/2017/03/08/positron-discontinued/ - https://mozilla.github.io/geckoview/ https://mozilla.github.io/geckoview/ (official but Android-only) - https://github.com/mozilla/qbrt https://github.com/mozilla/qbrt It may also be worthwhile reading about CEF which has become something of a defacto standard: https://en.wikipedia.org/wiki/Chromium_Embedded_Framework https://en.wikipedia.org/wiki/Chromium_Embedded_Framework