I’m sure they’ll do it eventually. This is probably a matter of priorities, and their message is just bad wording.
-
-
In their defense, if you break stuff with no transition period it's a valid statement. It would be like us removing ActiveX with no IE11 in box. So technically what they're saying is true.
4 replies 0 retweets 0 likes -
Replying to @gregwhitworth @simevidas and
Also, the add-on issue is one of the most common negative statements I'm seeing from customers regarding 57. A transition period probably would have been good.
1 reply 0 retweets 0 likes -
Replying to @gregwhitworth @simevidas and
Addons knew this was coming for more than a year. Previous releases also supported the new API. There was a long transition period already.
3 replies 0 retweets 1 like -
Replying to @ManishEarth @gregwhitworth and
https://blog.mozilla.org/addons/2015/08/21/the-future-of-developing-firefox-add-ons/ … was nearly 27 months ago, though didn't yet have an exact timeline.
1 reply 0 retweets 2 likes -
Replying to @davidbaron @ManishEarth and
It's not about length of time, it's how much effort goes into building a bridge and helping people cross it.
2 replies 1 retweet 1 like -
Replying to @wycats @ManishEarth and
I think
@deadsquid and team have some a lot of good work on that.1 reply 0 retweets 1 like -
Replying to @davidbaron @ManishEarth and
I don't mean to impugn anyone's work. I just don't think avoiding this negativity was a priority. So here it is.
1 reply 0 retweets 0 likes -
Replying to @wycats @davidbaron and
I'm hopeful that other positive aspects of 57 will overcome this issue. But it didn't need to be quite so big of a gamble :)
1 reply 0 retweets 0 likes -
Replying to @wycats @davidbaron and
If OSX was able to run OS9 apps in high fidelity, anything is possible ;)
2 replies 0 retweets 0 likes
Bottom line: I think it's possible to be introspective about ways this could have gone better without impugning people's work or feeling like it's an "us vs. them" situation. Which will make next time better.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.