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://brianbondy.com/blog/174/the-road-to-brave-10
Why do you write "probably... based on... relationship ended"? Brave as a startup does not have time for feels not realz, pathos-over-logos nonsense. I recommend you avoid it in your work efforts too.
But, I always recommend Brave for less-technical folks. It just works! My FF setup includes a number of extensions, some of which need a bit of tuning to be useful. Then you have to deal with issues in websites that just don't properly support FF, etc. My grandmother can install Brave and simply start browsing. Things just work without extra config or tinkering.
