Firefox is genuinely quite a good option. There are some Google-driven web proposals that they've refused to implement[0] (I'm sure I disagreed with some of them, though I forget which), but overall I've found that I've never really had to think about the browser: it's just a medium for the web.

They do offer some integrated services (which some would denote as bloat), though unlike Chrome, they do let you actually turn things off, which I'm very appreciative of -- they don't seem to be nearly as forceful as Google, who recently added a 4GB download to every Chrome install[0].

As I grow older, I find myself becoming more and more appreciative of platforms which don't try to redefine the problem scope, and instead just provide a platform for other things. GrapheneOS does this perfectly too.

[0]: https://mozilla.github.io/standards-positions/ [1]: https://www.malwarebytes.com/blog/news/2026/05/google-chrome...

▲

tech234a a day ago | parent [-]

And some of these proposals are available as polyfill browser extensions for Firefox

	▲	tentacleuno 6 hours ago \| parent [-]
		That's great from a user perspective, sure. From my perspective, with all of these different web APIs, I imagine Mozilla are walking a tightrope: if they refuse to implement all of them, there's a good chance that websites will ask the user to use Chrome, pushing it further into obscurity. Go too far, however, such as implementing Google-driven proposals like Topics, and you weaken the privacy advantages of the browser. I'm glad that they take both a moral and technological stance here - someone needs to.