5 ms·

I've been using Brave. I like it because it's not Google, but cannot comment on what's under the hood.

by awicz 6y ago

easytiger 6y ago
It's Chromium
cheph 6y ago
> I've been using Brave. I like it because it's not Google, but cannot comment on what's under the hood. It is just as much Google as Vivaldi is google because both uses Chromium.
- dsissitka 6y ago
  It isn’t. For example, Brave has committed to supporting the web request API after Manifest V3 is released. Vivaldi is abandoning it.
  - fsflover 6y ago
    At some point supporting everything Google abandoned becomes too expensive. I wonder what happens with Brave then.
  - square_usual 6y ago
    Cynically speaking, it won't matter if Brave continues to support the web request API, since all the other chromium variants aren't going to be. Once the market for extensions is 99% unable to support an API, it won't matter if the remaining 1% still does; developers simply won't target it.
  - Ndymium 6y ago
    What's your source on Vivaldi abandoning it? Last I heard they hadn't chosen yet. If they go full Manifest V3 then I'll have to abandon my thoughts of returning to Vivaldi (on Firefox now but there are some annoyances).
    - dsissitka 6y ago
      I believe it's the follow up to the piece you're thinking of. Here's the original: https://vivaldi.com/blog/chromium-ad-blockers-choice/ https://vivaldi.com/blog/chromium-ad-blockers-choice/ And here's the follow up: https://vivaldi.com/blog/ad-blocker-vivaldi-browser/ https://vivaldi.com/blog/ad-blocker-vivaldi-browser/ > First, Google decided to push on with discontinuing APIs used by several content blockers from the extension manifest v3. At the time, we made a promise to find a solution. > > Keeping support for the affected extensions (as with anything that gets discontinued in Chromium) would have been hard. Google usually removes most of the code a discontinued feature depends on and refactors anything that code relies on. So after a few versions, you end up with a patch that’s tough to apply every time. I am reaching a little but their use of past tense makes me feel like they've decided.
      - Ndymium 6y ago
        Hm, sad. :/ Will have to wait and see. Would be a shame if they went along with it.

I've been using Brave. I like it because it's not Google, but cannot comment on what's under the hood.

by awicz 6y ago

I've been using Brave. I like it because it's not Google, but cannot comment on what's under the hood.

easytiger 6y ago

It's Chromium

cheph 6y ago

> I've been using Brave. I like it because it's not Google, but cannot comment on what's under the hood. It is just as much Google as Vivaldi is google because both uses Chromium.

dsissitka 6y ago
It isn’t. For example, Brave has committed to supporting the web request API after Manifest V3 is released. Vivaldi is abandoning it.
- fsflover 6y ago
  At some point supporting everything Google abandoned becomes too expensive. I wonder what happens with Brave then.
- square_usual 6y ago
  Cynically speaking, it won't matter if Brave continues to support the web request API, since all the other chromium variants aren't going to be. Once the market for extensions is 99% unable to support an API, it won't matter if the remaining 1% still does; developers simply won't target it.
- Ndymium 6y ago
  What's your source on Vivaldi abandoning it? Last I heard they hadn't chosen yet. If they go full Manifest V3 then I'll have to abandon my thoughts of returning to Vivaldi (on Firefox now but there are some annoyances).
  - dsissitka 6y ago
    I believe it's the follow up to the piece you're thinking of. Here's the original: https://vivaldi.com/blog/chromium-ad-blockers-choice/ https://vivaldi.com/blog/chromium-ad-blockers-choice/ And here's the follow up: https://vivaldi.com/blog/ad-blocker-vivaldi-browser/ https://vivaldi.com/blog/ad-blocker-vivaldi-browser/ > First, Google decided to push on with discontinuing APIs used by several content blockers from the extension manifest v3. At the time, we made a promise to find a solution. > > Keeping support for the affected extensions (as with anything that gets discontinued in Chromium) would have been hard. Google usually removes most of the code a discontinued feature depends on and refactors anything that code relies on. So after a few versions, you end up with a patch that’s tough to apply every time. I am reaching a little but their use of past tense makes me feel like they've decided.
    - Ndymium 6y ago
      Hm, sad. :/ Will have to wait and see. Would be a shame if they went along with it.