"uBOL is entirely declarative, meaning there is no need for a permanent uBOL process for the filtering to occur, and CSS/JS injection-based content filtering is performed reliably by the browser itself rather than by the extension."
Yes.
What I don't know is:
1) whether their implementation of declarativeNetRequest has that arbitrary limitation
2) whether uBO Lite ships the same (limited) filters in the Firefox release.
I'm guessing 2) is true for simplicity, but that's purely a guess.
4 days ago the Chromium developers proposed upping the limit for certain types of declarativeNetRequest rules based on data AdGuard provided on real world rule lists. https://docs.google.com/document/d/1srkkCJkl4X2KOOUwnpDd-kvm...
But there will be a bunch of posts in this thread about people bemoaning Firefox because they have to have thousands of tabs open all at once everyday and Firefox renders them a second or two slower. There will also be people who will complain that the dev tools aren't exactly like what they learned in college/their boot camp so they can't spend dozens of minutes learning the Firefox tools so they can make their CRUD SPA can load megabytes of JSON outside of Chrome
Who wouldn't? It's one less version to maintain, and you're not going to stop maintaining the one most people use.
To some extent I have to ask - who cares that Chrome is more broadly used? That never stopped Firefox and its extensions from becoming popular in the first place. All it took for Firefox to rise was the competition being crap, and well the competition is becoming crap. Chromium's monopoly doesn't stop a few contrarian developers from continuing to keep their websites Firefox compatible.
No, it simply declares the goal of that add-on: to fully comply with declarative ways of MV3 AND its limitations, and no uBO extended features that need workarounds to be implemented.
He's more strict to Lite than full version:
- https://github.com/uBlockOrigin/uBOL-home/issues/17
- https://github.com/uBlockOrigin/uBOL-home/issues/6#issuecomm...
Firefox has done this to me multiple times. As someone who uses a web browser as a tool for both business and pleasure, and as someone who does not appreciate flag days forced on me for no good reason, I am perfectly happy and have been encountered far fewer surprises with a chromium fork.
That latter category of breakage, which Firefox has never done, and has no motive to, is the reason I will never use the shameless antitrust-case-in-waiting Chrome, or any of it's pseudo-independent offspring.
This won't be remedied because it is the point of Manifest V3. Google is an ad company. The next step is the Web Integrity API, where the website can block you if you have even uBOL.