3 ms·

I wonder what will Vivaldi do. They say that their built-in content blocker is "good enough" that you supposedly don't need uBO (I very much disagree) but they

by grishka 4mo ago

I wonder what will Vivaldi do. They say that their built-in content blocker is "good enough" that you supposedly don't need uBO (I very much disagree) but they also keep MV2 extensions working to this day.

pseudalopex 4mo ago
Vivaldi said We will keep Manifest v2 for as long as it’s still available in Chromium.[1] They kept it before now because it was little effort. [1] https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/ https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-futur...
maxloh 4mo ago
They can only support MV2 extensions as long as Google continues to maintain them. Their tech stack is heavily JavaScript-focused, as their entire UI is written in JavaScript.
- zamadatix 4mo ago
  How is it half of HN is convinced Firefox can compete with Chrome in its entirety and the other half is convinced nobody can possibly maintain a single additional API version on Chromium?
  - maxloh 4mo ago
    It's about the tech stack, IMO. Chromium is a moving target to maintain compatibility with, which is difficult for a team that doesn't have much C++ experience. As a counter example, Brave is heavily invested in C++ and Rust, and I believe they could handle that work much better.
    - grishka 4mo ago
      Can't Chromium-based browser developers work together to fork the entire thing? Ideally becoming independent of Google altogether.
      - pseudalopex 4mo ago
        It would be much spent and not much gained in their eyes.
    - zamadatix 4mo ago
      Sure but even Vivaldi has a few C++ folks on the dev team, how many more is it to maintain an existing API to changes in the codebase, especially when any of the hard parts of that work only need be done once among all of the forks. Even if they don't want to handle it directly, this is the kind of thing a single sponsor can pay Igalia for, who have shown the ability to make entire new Chromium subsystems like MathML. There is no shortage of C++ browser developers in the world to do maintenance work.

by grishka 4mo ago

pseudalopex 4mo ago

Vivaldi said We will keep Manifest v2 for as long as it’s still available in Chromium.[1] They kept it before now because it was little effort. [1] https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/ https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-futur...

maxloh 4mo ago

They can only support MV2 extensions as long as Google continues to maintain them. Their tech stack is heavily JavaScript-focused, as their entire UI is written in JavaScript.

zamadatix 4mo ago
How is it half of HN is convinced Firefox can compete with Chrome in its entirety and the other half is convinced nobody can possibly maintain a single additional API version on Chromium?
- maxloh 4mo ago
  It's about the tech stack, IMO. Chromium is a moving target to maintain compatibility with, which is difficult for a team that doesn't have much C++ experience. As a counter example, Brave is heavily invested in C++ and Rust, and I believe they could handle that work much better.
  - grishka 4mo ago
    Can't Chromium-based browser developers work together to fork the entire thing? Ideally becoming independent of Google altogether.
    - pseudalopex 4mo ago
      It would be much spent and not much gained in their eyes.
  - zamadatix 4mo ago
    Sure but even Vivaldi has a few C++ folks on the dev team, how many more is it to maintain an existing API to changes in the codebase, especially when any of the hard parts of that work only need be done once among all of the forks. Even if they don't want to handle it directly, this is the kind of thing a single sponsor can pay Igalia for, who have shown the ability to make entire new Chromium subsystems like MathML. There is no shortage of C++ browser developers in the world to do maintenance work.