undefined | Better HN

0 pointsljoshua6y ago0 comments

I use Brave as my daily driver, but this trickled down into Brave as well this morning. I was confused for a minute what I had done with a subdomain on one of my sites, and then got very frustrated when I realized the Chromium team had put this back in place. A few #omnibox... tweaks later and I have it back, but it is certainly annoying.

0 comments

2 comments · 1 top-level

danShumway6y ago· 1 in thread

This is why forking Chromium is not a solution. Unless a team is committed to maintaining that fork, eventually they'll be forced to merge in any of the changes that Google wants to push.

The only way a Chromium fork works is if the team is willing to stop merging after they fork and take over development themselves.

magicalist6y ago

> This is why forking Chromium is not a solution

Brave isn't a fork, though, it's a downstream consumer of Chromium.

> The only way a Chromium fork works is if the team is willing to stop merging after they fork and take over development themselves.

I mean, that's what a fork is, so yeah?

I don't think Brave demonstrates much about that situation.

j / k navigate · click thread line to collapse