Wow, I just typed "npm install --global web-ext", "web-ext --version" and a few other expressions that tutorial offers into Firefox (location bar and console) and I can confirm any add-on one has currently in mind magically turns into a fully working WebExtension. Furthermore the screen turns into a portal and a unicorn with a pot of gold jumps out.Reflective wrote:...
I doubt if many devs spent time recoding their extensions in the way that you mentioned. Mozilla has already made test samples of web-ext available which can be cloned according to the following tutorial. Or at least that's the way I read it.
Similarly, the abundance of such tools would seem to contradict your opinion that Mozilla has 'zero compassion' for people.
Back to topic.
I guess you are not an add-on developer or a software developer of any kind, right? It is easy to say this and that without knowing how things work or used to work, so believe those, who actually are familiar with add-on development of the last 5-10 years. Otherwise please prove us wrong and explain how current add-on developers should gain anything from these examples: https://github.com/mdn/webextensions-examples
In case you have not read Mozillas "Comparison with XUL/XPCOM extensions":
https://developer.mozilla.org/en-US/Add ... extensions
...
Compared with XUL/XPCOM extensions, WebExtensions provide much more limited options for the add-on's UI, and a much more limited set of privileged JavaScript APIs.
WebExtensions can only access web content by injecting separate scripts into web pages and communicating with them using a messaging API (note, though, that this is also true of XUL/XPCOM extensions that expect to work with multiprocess Firefox).
@Frank
Your comment made my day.