Chrome’s extensions were isolated, easy to develop and had a permissions system in place.
To this day Firefox is still lagging behind in its isolation. For example Chrome can disable extensions in Incognito, but Firefox does not.
Also if you’re not paying attention, Chrome won and it’s nearly a monopoly. This means browser extensions get developed for Chrome first. Having similar APIs helps with migration.
I view the change as a good thing because I can finally develop my own extensions without headaches.
That is being worked on though:
> The first batch of changes to not run extensions in private browsing mode by default landed, this is still behind a preference.
https://blog.nightly.mozilla.org/2019/01/31/these-weeks-in-f...
Solution: change profile to launch another browser instance without extensions.
Go to "about:profiles" in the address bar, or configure shortcuts in your OS to launch browser with different profiles: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Mul...
Not me. If the new extension system didn't present a loss of important (to me) functionality, then I'd think it was a good thing.
But the loss of functionality happened, and that change is what makes the new Firefox unsuitable for me, so I stopped using it (and I never used Chrome).
