&gt; If you&#x27;re an add-on developer yourself and are concerned about APIs you need<p>I&#x27;m actually not, and one reason is because I&#x27;ve seen over the years how extension authors have to keep up with the churn constantly breaking things, and that&#x27;s not a pool I want to wade into.  I&#x27;m amazed that, e.g. the Pentadactyl authors have the time and patience to do so.<p>So, if this new API stabilizes things long-term, that&#x27;s fantastic.  I would love to have extensions that never break again.<p>But forgive me for being skeptical, because with the CADT-style development models ruling the world nowadays, what usually happens is, the old API is deprecated and dumped before the new one has feature parity, leaving authors and users hanging.  And with Mozilla&#x27;s trend of imitating Chrome, this seems even more likely.<p>I can hear the cries now of, &quot;The old API is too hard to maintain, so we&#x27;re removing it in Firefox 72.  We hope to reach approximate feature parity by Firefox 84, but we do not plan to reimplement all features in the new API.  Regrettably, this will prevent some addons from being ported to the new API,&quot; with the implied, &quot;But &#x27;no one&#x27; [compared to the number of users on the Internet] was using those addons anyway, so who cares.&quot;  And cue me switching browsers.<p>Please prove me wrong.  :)