Elektrine lite

← Feed

@XLE@piefed.social

2026-04-24 15:58 UTC

> isn't ublock's filtering compiled to webassembly? From my unprofessional glance ar their repository, it uses a little, but not much. Take a look at [their code](https://github.com/gorhill/uBlock/tree/master/src/js); all or most of the filtering is done in JavaScript, the webassembly appears to be just ~~one~~ two modules. (It's in the "wasm" folder near the top of the list). _(Edit: I was looking at outdated code; the newer version uses more, but IMO pales in comparison to the [JavaScript filtering logic](https://github.com/gorhill/uBlock/blob/master/src/js/static-filtering-parser.js))_ > seems a bit dangerous though to risk for a browser with so small market share Waterfox has a much smaller market share and _much_ smaller budget, and was able to clear this with search partners just by promising not to block ads on them by default.

Replies (1)

  • @WhyJiffie@sh.itjust.works 2026-04-24 21:54

    > Waterfox has a much smaller market share and *much* smaller budget, and was able to clear this with search partners just by promising not to block ads on them by default. my point is not actually about search providers, but more generally websites intentionally breaking support for gecko based browsers. waterfox itself is too little, most developers don't even know about it I think. but firefox is the flagship/reference gecko browser, with more of a measurable number of users. if they implement a good ad blocker in the base browser, that could discourage advertising related sites from serving/supporting this browser. brave is different in that it uses chromium, which the sites just happen to support already because of chrome. but firefox support is often not a priority even today

    Open ##1714510