4 ms·
Here they defend the decision to adopt WebExtensions even though they're now reduced to chasing Chrome's whims. But maybe all the disruption and pain can be jus
by guelo 4y ago
Here they defend the decision to adopt WebExtensions even though they're now reduced to chasing Chrome's whims. But maybe all the disruption and pain can be justified because there has been a flood of cross-platform plugins that were previously unavailable in Firefox. I don't have any data but my sense is that there are a lot fewer extensions than their used to be. There is definitely less plugin innovation happening since, as with most Google APIs, it is less powerful, less transparent, more locked down. There is also the question of differentiation, what is Firefox's value if it is but another Chrome clone?
- sp332 4y agoIt's a superset of Chrome's functionality. E.g. https://github.com/w3c/webextensions/issues/134 https://github.com/w3c/webextensions/issues/134. The Web Extension API in Firefox is generally a lot bigger than Chrome's, so there's plenty of differentiation and I wouldn't call it a clone.