This is a choice we made. As I wrote in my last reply, I think we would have died trying to get Gecko/Graphene with a Web front end up to competitive scratch vs. Chrome (nm Firefox).
A Firefox fork would have gone over badly with some potentially large number of Mozilla/Firefox fans, and we'd still lack key elements not part of the Mozilla open source (at the time, e.g., Adobe's CDM for HTML5 DRM). On the upside we'd have more UX customizability.
But our choice of Chromium/Blink (via Electron, so we had Web front end upside without Firefox extensions) was not a slam dunk choice. It involved trade-offs, as all engineering does. One downside is we have to audit and network-test for leaks and blunders, which often come from Chromium upstream:
Huh, I was under the impression that you were forking Chromium itself instead of building over Electron. Or are you talking about a past, post-Gecko decision that had to be dropped as well?
https://github.com/brave/brave-browser/wiki/Deviations-from-...
This is a choice we made. As I wrote in my last reply, I think we would have died trying to get Gecko/Graphene with a Web front end up to competitive scratch vs. Chrome (nm Firefox).
A Firefox fork would have gone over badly with some potentially large number of Mozilla/Firefox fans, and we'd still lack key elements not part of the Mozilla open source (at the time, e.g., Adobe's CDM for HTML5 DRM). On the upside we'd have more UX customizability.
But our choice of Chromium/Blink (via Electron, so we had Web front end upside without Firefox extensions) was not a slam dunk choice. It involved trade-offs, as all engineering does. One downside is we have to audit and network-test for leaks and blunders, which often come from Chromium upstream:
https://x.com/BrendanEich/status/1898529583546421322