Anyone here uses Firefox as their main browser?
Just a curious curiosity.
Not to mention that Chrome is planning to remove adblockers next year, so I have heard.

I use it as my main browser.

I do. I use it on PC because it has all my add-ons and bookmarks and whatnot (EDIT: and I prefer the way the UI handles a large number of tabs over how chrome does it), and I use it on my Android phone because I'm dumb and too lazy to switch. Though one (rarely used) benefit of using Firefox on both is I can access tabs already open on one device from the other device as well.

kora_viridian said:
I do. Firefox and its predecessors have been my daily driver since throbbing-N Netscape. For a few years my copy said "Iceweasel" on the box, but it was really Firefox inside. Once everybody agreed to IP freely, it said Firefox again.

I think that mostly has to do with Google requiring add-ons to support "Manifest v3". One of the things that means, I think, is that add-ons aren't supposed to go out and download stuff on their own - which is how most of the current ad-blockers update their lists of what to block.

Around summer 2022, Google had penciled in the date of this change as the end of 2022. A few months ago, they pushed it out to mid-2023. I haven't checked on the status lately.

On the other hand, I also remember hearing "Chrome is killing ad-blockers" before. I think it was when the interface for add-ons changed from either the Netscape plugin API (Firefox) or Pepper API (Chrome) to the WebExtensions API (Firefox, Chrome, others). The ad-blocker developers figured out how to work with the new API and life went on.

Yes, Manifest v3 is what's breaking it, but the change that's breaking ad-blockers is different. Think about it, if extensions couldn't download stuff on their own, then none of them would be able to update at all. Having tons of out of date extensions that need to be updated would be a much bigger security problem. The real change that's hitting ad-blockers is a change to the "webRequest" feature, which is hard to see having any reason other than interfering with ad-blockers. Oversimplifying things, what the change does is it requires ad-blockers(and other extensions) to declare what they're going to do to something they suspect to be an ad before they're allowed to check to see if it is actually an ad.

That's not to say that Manifest v3 is completely pointless, there are a lot of other good changes, but bundling invasive or restrictive garbage with every improvement they make is what tech companies do.

I use Firefox since 2006 and so far never had any problems with it - no reason to switch

I've used it for years now, while keeping chrome for some separate tabs here and there.

Brave, Chrome, Chromium, Firefox, Dolphin, Opera, SeaMonkey, Vivaldi, mostly, depending on device/OS. I guess that's every mainstream one except Edge and Safari. ;)
Seriously though, Chrome on Android is ironically worst version of it.

There may come a point where you have an interface JUST for uBO/ABP-style plugins and have it audited+signed like we had to do for bootloader chains (and auditing is weak sauce on Intel's Secure Boot code). There comes a point where it's making more sense to make the browser a bunch of layers that can be swapped out. The current mess in Chromium family is not helping with long-term sustainability. That one thing where you could do a blocklist but it was limited to simplistic patterns, AND extremely limited in number of expressions was just a slap in the face to filter users.

They really can't maintain support for the legacy interface, either. Technical reasons but it defeats the entire point, for a big one. Think of the bandaid pulled when 40-bit SSL support had to be dropped on all sites. Or when Firefox pulled rug out many other times for plugin authors and preferred user interfaces instead of that dinosaur example. XD