To counter all those throwaway accounts created to praise Brave, I have to say that I have no intention to use it because it's based on Chromium. Single-culture is bad even if your intentions are good. I never used Chrome either and have lived through ups and downs of Mozilla since 2002 when I ditched IE6.
I wish Firefox tech was easier to integrate into other browsers, so that we could have a more balanced ecosystem.
I don't want to accuse anyone of astroturfing, but the comments in this thread seem to be eerily positive and very marketing-y. Maybe it's my skepticism of everything crypto-related being incredibly biased one way or another.
Disclaimer: I’ve been using/testing Brave for the last few years. I've seen it evolve from what was basically a proof of concept running in Electron to what it is today.
I believe if you care to do some research, you'll see that the Brave team has put in the work to be taken seriously.
I get why people are skeptical, especially in this day and age. But the concept for Brave and disrupting the surveillance capitalism known as ad tech goes back to 2013; Brave is not a johnny-come-lately thing[1].
This was started by Brendan Eich, the same guy who created JavaScipt and who started Mozilla which gave us Firefox; it's not like he's someone who doesn't understand how this stuff works.
Every potentially unpleasant Brave feature is easy to disable (and often by-default disabled). Is is very good at ad-filtering, snappy and responsive, stable, can be audited (opensource)... and the underlying ways to provide for creators/publishers (and also people liking/needing advertising) are clever and disruptive.
Brave is worth a try.
I'm not paid for this (and there is no 'conflict of interest').
For whatever reason firefox seems to actively sabotage any attempts to reuse their technology. The one area where people were reusing it, mozjs has been nothing but heartaches for everyone involved because they literally break part of their API's with every release. Back a couple years ago they changed the library bindings from C to C++ basically forcing all their users to write their own shims even if they were C based projects.
This is likely a large part of why they are losing, I remember showing people how it was possible to create a web browser with a couple clicks and a line or three of code using the IE activeX component in delphi around ~2000. Back then it was possible to do similar things with KHTML.
So instead of a nicely structured project its got layers of crap, even in the build system where you have to dig through python wrappers around automake, etc just to figure out simple things where some options are in one place and others are in another depending on whether they bothered to convert one part of the project or not.
I wish Firefox tech was easier to integrate into other browsers, so that we could have a more balanced ecosystem.