[cpeterso]

Maintaining out-of-tree patches for a project as large and quickly-changing as Chromium will be a lot of work. I know someone who worked on Amazon's Silk browser team and they had an engineer (rotation) working working full-time to keep their Chromium fork up to date within Google's upstream. Brave doesn't have nearly the resources that Amazon does.

[UberFly]

Yea you've seen it tried in projects like Waterfox and Palemoon and it eventually becomes too much to deal with. (Following the old Firefox addons system that is)

[TremendousJudge]

Yeah it's clear that was never going to work -- the whole point of dropping the old addons was making big architectural changes that weren't possible with the old APIs. You can't merge the new architectural changes and the old APIs without running into the issues they were trying to avoid by removing the old APIs in the first place.

[marwis]

There are few projects and companies that do exactly that, including CEF open source project. Perhaps they should join forces and make a joint OpenChromium project.