>>547232
>Webextensions can't change a browser nearly as much as traditional add-ons can
And how would you know that, considering they aren't even released yet and the list of APIs is far from final?
>Stuff like vimperator and noscript simply will not be possible with webextensions
Except Mozilla explicitly said that they are working on providing APIs to support those two.
>It means that the age of the power-user is over for Firefox.
Even if it were the case, XUL/XPCOM extensions are still going to be supported for years, it will take over a year for us to even start seeing the switch of internal functions to HTML.
Webextensions≠Chrome extensions, they are going to provide a lot more power to developers, though to be fair we still have to wait and see if that power is going to be comparable to that of XUL/XPCOM.