3 ms·
I indeed looked for alternatives and they're just not there yet. The more I read, the more APIs turn out to be missing or buggy, making it impossible for add-o
by lucb1e 9y ago
I indeed looked for alternatives and they're just not there yet.
The more I read, the more APIs turn out to be missing or buggy, making it impossible for add-ons to be made (if the developer is active in the first place). I just don't understand this. Firefox was built on the extendible principle and they're now going back to "v0.2 beta" in that regard.
This process should have taken years to mature the new APIs before dropping support for the old method.
- Sylos 9y agoSo, look at this graph: http://netmarketshare.com/report.aspx?qprid=1&qpaf=&qpcustom=Firefox&qpcustomb=0&qpsp=200&qpnp=24&qptimeframe=M http://netmarketshare.com/report.aspx?qprid=1&qpaf=&qpcustom... Notice that major bump in August 2016 and after? Firefox 48 was released on the 2nd August 2016. This was the first release to ship the new multiprocess architecture. And this new architecture also already required breaking all extensions. They could not have shipped it this early without knowing that the switch to WebExtensions will cut off the multiprocess-incompatible extensions. And they needed to get multiprocess shipped. Had that graph continued as in the half year before that, we would now have negative user numbers.