4 ms·

No they don’t, they manually merge code from upstream if they like it. Since Brave doesnt like it they wont merge it.

Dudemeister_ 5y ago
Won't this create a problem for them when it comes to the extension store since no new v2 extensions will be able to be deployed there even though other chromium based browsers support them?
- detaro 5y ago
  Firefox will move to v3 while retaining the old webrequest APIs, so there will extensions around that would work.
celsoazevedo 5y ago
If Google makes enough changes that eventually makes it impossible to merge upstream code while maintaining compatibility with the old APIs, then Brave and everyone else will either be stuck with old and unpatched Chromium versions or they'll have to waste resources to keep things working. Not everyone has the resources to maintain their own Chromium fork and it's not easy to keep up with Google, Microsoft, Samsung, etc. Just look at Firefox.
- WA9ACE 5y ago
  They already de-google the entire codebase. You can see which parts are removed here https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove) https://github.com/brave/brave-browser/wiki/Deviations-from-... and they keep up quite well.
  - celsoazevedo 5y ago
    Yeah... what happens when Google decides something important can't work without one of the disabled features? Look, Google controls Chromium and they have the resources (and incentive?) to keep these smaller browsers running in order to keep up with them.
mintplant 5y ago
That's not actually true. Brave's system uses a Chromium commit hash as a base, then applies patches on top of that. They'll have to manually move the old API implementation into patches and continue to maintain it there. Source: I've collaborated with / worked on Brave in the past.
- vmception 5y ago
  Sounds like they need a more comprehensive response with this move

Won't this create a problem for them when it comes to the extension store since no new v2 extensions will be able to be deployed there even though other chromium based browsers support them?

detaro 5y ago
Firefox will move to v3 while retaining the old webrequest APIs, so there will extensions around that would work.

celsoazevedo 5y ago

If Google makes enough changes that eventually makes it impossible to merge upstream code while maintaining compatibility with the old APIs, then Brave and everyone else will either be stuck with old and unpatched Chromium versions or they'll have to waste resources to keep things working. Not everyone has the resources to maintain their own Chromium fork and it's not easy to keep up with Google, Microsoft, Samsung, etc. Just look at Firefox.

WA9ACE 5y ago
They already de-google the entire codebase. You can see which parts are removed here https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove) https://github.com/brave/brave-browser/wiki/Deviations-from-... and they keep up quite well.
- celsoazevedo 5y ago
  Yeah... what happens when Google decides something important can't work without one of the disabled features? Look, Google controls Chromium and they have the resources (and incentive?) to keep these smaller browsers running in order to keep up with them.

mintplant 5y ago

That's not actually true. Brave's system uses a Chromium commit hash as a base, then applies patches on top of that. They'll have to manually move the old API implementation into patches and continue to maintain it there. Source: I've collaborated with / worked on Brave in the past.

vmception 5y ago
Sounds like they need a more comprehensive response with this move