Unrelated but about Brave and interesting to me: I recently found myself having a large upstream project that I need to maintain some custom patches for, and there's a need for deeper customizations and I worry that my rudimentary system of applying .patch files will turn into an unmaintainable nightmare of merge conflicts after every rebase. I was thinking about possible solutions, and it occurred to me that Brave being Chromium-based must have this same challenge but an order of magnitude more difficult, so I looked for their code to see how they solved this issue.<p>It's pretty interesting! They do basically the same thing for core Chromium, applying a (big) set of patches[1].<p>Incidentally, I'd be interested to hear any ideas/approaches to this problem. I'm guessing if there was something clearly better, Brave would be doing it, but it seems like there <i>should</i> be a better way even if I can't think of one.<p>[1] <a href="https://github.com/brave/brave-core/tree/master/patches">https://github.com/brave/brave-core/tree/master/patches</a>