4 ms·
I don't think it's a preference thing. I don't think Vivaldi, or Brave, or any other company whose main product is a browser, can have the income to pay 1000+ e
by mort96 4y ago
I don't think it's a preference thing. I don't think Vivaldi, or Brave, or any other company whose main product is a browser, can have the income to pay 1000+ engineers to work on the codebase to keep up with the pace of Google.
Maybe it should at the very least be a wake up call to companies which can't afford the engineer-hours it takes to maintain a Chromium fork.
- madamelic 4y agoThere's enough of them and I am sure non-affiliated as well, they could likely scrape together enough engineering 'power' to maintain their own sane fork of Chromium. They don't need to keep pace feature-wise. I don't need a featureful browser, I want a browser that performs well.
- nemothekid 4y ago>They don't need to keep pace feature-wise. Last I looked into it; the problem wasnt with features. The Chrome code base is very dynamic and if you fall behind then it becomes very hard to pull upstream patches due to the pace at which things get refactored.