Re:Firefox 57 as the first release where only WebExtensions ...
by pseudalopex on Saturday February 18, 2017 @06:19PM
(#13677234)
WebExtensions are multiprocess-compatible by design, but so are Jetpack SDK extensions unless they use certain APIs. The main rationale for WebExtensions was to make it easier for extensions to support multiple browsers -- implicitly, because new extensions were increasingly Chrome-first or Chrome-only.[1]
The problem is less the end goal and more how Mozilla is handling the transition. Developers have identified missing APIs, but they don't know when or if they'll be implemented.
Option D: Define "good enough" in terms of specific features. Tell developers they'll have six months after that to migrate. Put out an ESR that fully supports both old and new APIs to give users a smooth transition. If you don't have the resources to do that, explain the tradeoffs in detail and apologize profusely.
The problem is less the end goal and more how Mozilla is handling the transition. Developers have identified missing APIs, but they don't know when or if they'll be implemented.
Option D: Define "good enough" in terms of specific features. Tell developers they'll have six months after that to migrate. Put out an ESR that fully supports both old and new APIs to give users a smooth transition. If you don't have the resources to do that, explain the tradeoffs in detail and apologize profusely.
[1] https://blog.mozilla.org/addons/2015/08/21/the-future-of-dev...