We all know too well what happens when a backwards-breaking change is imposed without strong functional justifications : most developers don't actually put the effort to upgrade and as a result the vast majority of extensions break. Case in point : python modules, after tremendous effort and years of waiting about 2/3rd of the existing modules have been ported from python 2 to 3.
This is relatively "mitigated" in the case of add-ons because backwards-incompatibility has become the norm so old add-ons are likely to break anyway at some point, but this still seems like a very bad idea for Mozilla to kill a large portion of their ecosystem in that single move, especially if in the bunch are very differentiating extensions like Tree Style Tabs.
Justifying the decision by becoming even more interchangeable with Chrome is especially baffling, what is the strategic point of this?
This is relatively "mitigated" in the case of add-ons because backwards-incompatibility has become the norm so old add-ons are likely to break anyway at some point, but this still seems like a very bad idea for Mozilla to kill a large portion of their ecosystem in that single move, especially if in the bunch are very differentiating extensions like Tree Style Tabs.
Justifying the decision by becoming even more interchangeable with Chrome is especially baffling, what is the strategic point of this?