I’ve been curious about the Brave browser for a little while now, and I’ve switched to Brave for any Chromium-based browser stuff I do (testing, browsing on sites that don’t support Firefox, and so on).
Specifically, the study examined the browsers’ sending of data—including unique identifiers and details related to typed URLs—that could be used to track users over time. The findings put the browsers into three categories with Brave getting the highest ranking, Chrome, Firefox, and Safari receiving a medium ranking, and Edge and Yandex lagging behind the rest.
A few of my colleagues have been raving about the relatively new, Chromium-based Brave browser lately, so I decided to try it out.
I initially didn’t pay much attention because I’m pretty happy using Firefox as my primary browser. That said, I like a browser that blocks tracker crud on the Web, so I thought I’d try it out.
The biggest plus for me is that the browser blocks trackers out of the box. It’s one of the reasons I’m a big Firefox fan – pretty robust tracker blocking from the start.
Brave puts performance, and security at the forefront, literally, with indicators of how much the browser is blocking as you journey across the Web, and how much time it seems to be saving as your browse:
I haven’t really compared Brave’s blocking stats with Firefox’s (I’m not sure if I can really compare them directly given that I just see totals, not a breakdown), but it is gratifying to see that value go up.
In Firefox, I set my start page as about:protections so I see this data each time I start up my browser, too:
If anything, these values are great reminders of how much cruft is on the Web, degrading our browsing experience.
Another aspect of the Brave model is how it uses Basic Attention Tokens as a way to reward us consumers for visiting participating content creators’ sites.
I don’t fully understand how Brave Rewards work, but I like this idea of enabling consumers to make micro-contributions to content creators, and help support them. It’s a bit like Recurring Payments on WordPress.com.
That said, I intend doing some more research. The model intrigues me!
If you’re interested in trying the Brave browser out, here are a couple things I’ve discovered so far that may help you make the move from Chrome, if you’re a Chrome user:
Brave is Chromium-based, so it actually looks and feels a lot like Chrome;
You can install Chrome extensions in Brave, just like you do with Chrome;
Instead of using Google sync to sync between Brave browsers on different browsers, Brave has its own sync tool. This may be appealing if you don’t want Google at the heart of your browsing experience.
I’ve enjoyed using Brave so far. I’m not switching away from Firefox just yet, but I’m using Brave as my preferred Chromium-based browser, and it’s working well for me.
In the meantime, here are a couple posts that I’m going to read for broader perspectives on Brave:
In December 1990, an application called WorldWideWeb was developed on a NeXT machine at The European Organization for Nuclear Research (known as CERN) just outside of Geneva. This program – WorldWideWeb — is the antecedent of most of what we consider or know of as “the web” today.
In February 2019, in celebration of the thirtieth anniversary of the development of WorldWideWeb, a group of developers and designers convened at CERN to rebuild the original browser within a contemporary browser, allowing users around the world to experience the origins of this transformative technology.
My first browser was probably one of the early Netscape browsers (I loved those browsers), although it’s possible I may have started off with Microsoft’s Internet Explorer given how prevalent it was in those early days.
I love using Firefox as my primary browser. I prefer using it for a variety of reasons. Lately, though, I’ve noticed that it’s become a bit of a resource hog, and I can’t work out why? I’ve disabled add-ons that I don’t need, and it still uses about 1.4GB of RAM at a minimum for pages that Chrome uses a quarter of RAM for.
Has something changed in Firefox’s architecture? One thought I had is that maybe this has to do with something like page pre-fetching (I think Firefox does that), or something along those lines. I want to sort this out. Chrome seems to be so much better at resource management at the moment.
I love using Firefox as my primary browser. I prefer using it for a variety of reasons. Lately, though, I've noticed that it's become a bit of a resource hog, and I can't work out why?
