[iggldiggl]

One problem is that it doesn't work as simply as "all APIs this add-on uses are supported, so let's enable it" – they instead still insist on explicitly whitelisting every individual add-on. So a few really popular extensions are whitelisted and the long tail is left behind, even if it might work perfectly well or at least useable enough.

I have for example one small extension that I maintain, which is basically little more than a glorified page script which therefore doesn't use any special extension APIs at all. Despite that, it took months for it to be enabled, and if it wasn't as popular as it is I might still be waiting even today.

> the new browser is significantly snappier and uses less power in my experience.

Ha! From a cold start, on my phone launching the new Firefox (with less add-ons) and loading a page seems to take approximatively twice as long as on Firefox 68, and still ~50 % more than even on Firefox 55.

[iggldiggl]

Postscriptum: To be fair, after investigating a little more it seems that the cold start penalty with the new Firefox seems likely due to fixing a bug that meant uBlock and similar add-ons were previously unable to intercept the first few network connections that were happening right during startup.

So on the one hand fixing that bug makes sense and has some value, but on the other hand and in practice the increased startup time still feels rather quite annoying, too, given that my phone isn't the latest and fastest model.