3 ms·
More devs should support and use it, lest we be beholden to Chrome for the rest of time. Why support what already broke your work once without an actual transi
by protomyth 8y ago
More devs should support and use it, lest we be beholden to Chrome for the rest of time.
Why support what already broke your work once without an actual transition plan? They didn't have a full replacement ready to go when they got rid of XUL, and seemed that they didn't really care.
- larrik 8y agoI'm pretty sure he meant web devs, not plugin devs.
- protomyth 8y agoAnyone who ignores prior treatment of folks is foolish. Why would a web developer support one browser over others? They keep everyone honest by sticking to the middle road and not having a badge like "Works Best In FireFox".
- Jorge1o1 8y agoAnd yet there’s scores of websites that barely work on anything except Chrome because it’s obvious that’s what the devs are using.
- michaelmrose 8y agoThey announced web extensions in summer of 2015. https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ https://blog.mozilla.org/addons/2015/08/21/the-future-of-dev... At the end of August of 2018 they stopped supporting 52 ESR which is the last extended support release that supports the old addons. During the 3 years between a and b mozilla worked to provide support for flexible interesting addons which is why all the notable interesting addons I'm aware of have new versions. I'm sure that the will to port every useful addon in existence just isn't there but it seems challenging for firefox to move forward without ditching the old addons. Did you realize the new addon system was released over 3 years ago? It kind of seems as if perhaps as a user you were only peripherally aware of matters and derived an erroneous interpretation of events.