Confirmed users
130
edits
WebExtensions/FAQ: Difference between revisions
Wording
Wmccloskey (talk | contribs) (remove redundant stuff) |
Wmccloskey (talk | contribs) (Wording) |
||
| Line 12: | Line 12: | ||
In Jetpack's favor, it has a powerful module system similar to the one in node.js. However, given that JavaScript will soon have built-in support for modules, this won't be an advantage for long. | In Jetpack's favor, it has a powerful module system similar to the one in node.js. However, given that JavaScript will soon have built-in support for modules, this won't be an advantage for long. | ||
Finally, Jetpack doesn't solve the problem that add-on developers must | Finally, Jetpack doesn't solve the problem that add-on developers must maintain a different codebase for each browser. Basing WebExtensions off Chrome's API means that developers who stick to the common APIs will only have to maintain one codebase. | ||
=== Which add-ons will stop working after the deprecation? === | === Which add-ons will stop working after the deprecation? === | ||