Never use Chrome, but there are some reasons to use a Chromium fork browser.
On privacy, just using Pale Moon gives them like 10 bits of signal to id you with on top of all the other things they can use. That's huge. Brave looks like any other Chromium except with fingerprint randomization for lots of things.
Also the more Chromium forks there are the harder it is for Google to make changes because they have to keep the forks from splitting off on their own.
For example with the new manifest to limit adblocking, if Brave/Edge/Vivaldi/Opera don't accept that change then Google's 75% market share drops to maybe 60% or something like that and those others are virtually identical except with better features so it's easy for people to switch.
Google has already delayed manifest v3 by 4 months so far for this reason. They say "intently monitoring comments from the developer community to help inform our timelines" and what that means is "finding some way to do it without losing the forks".
You've got it backwards. Almost all google chromium and firefox browsers will implement MV3. Some might try to keep WebRequest from MV2, but they'll still follow google Web Extensions, and will have to either Hard Fork or do massive jumps through hoops to re-engineer it when google removes all support for MV2.
Never use Chrome, but there are some reasons to use a Chromium fork browser.
On privacy, just using Pale Moon gives them like 10 bits of signal to id you with on top of all the other things they can use. That's huge. Brave looks like any other Chromium except with fingerprint randomization for lots of things.
Also the more Chromium forks there are the harder it is for Google to make changes because they have to keep the forks from splitting off on their own.
For example with the new manifest to limit adblocking, if Brave/Edge/Vivaldi/Opera don't accept that change then Google's 75% market share drops to maybe 60% or something like that and those others are virtually identical except with better features so it's easy for people to switch.
Google has already delayed manifest v3 by 4 months so far for this reason. They say "intently monitoring comments from the developer community to help inform our timelines" and what that means is "finding some way to do it without losing the forks".
You've got it backwards. Almost all google chromium and firefox browsers will implement MV3. Some might try to keep WebRequest from MV2, but they'll still follow google Web Extensions, and will have to either Hard Fork or do massive jumps through hoops to re-engineer it when google removes all support for MV2.
https://www.theregister.com/2022/05/20/mozilla_opens_testing_for_manifest/
https://www.ghacks.net/2022/09/24/vivaldi-ad-blocker-manifest-v3/
https://www.ghacks.net/2022/09/29/brave-browser-manifest-v2-extensions-after-v3-update/
https://forums.opera.com/topic/50569/manifest-v3-opera/2?_=1682676951014&lang=en-US
https://blog.mozilla.org/addons/tag/manifest-v3/