News for hackers. Stuff that matters.
Re:Firefox 56: Last Stop Before Quantum by oblio on Friday October 06, 2017 @11:02AM (#15417297)
It's because of the killer combo of increased sandboxing, multi-process architecture and performance constraints.

I think they couldn't keep everything together with the degree of access old plugins had to Firefox internals. So at some point they had to rip off the band aid.

Re:Firefox 56: Last Stop Before Quantum by pseudalopex on Friday October 06, 2017 @02:18PM (#15419018)
Multiprocess already shipped. One of the reasons extension developers are frustrated is that Mozilla told them to make their XUL extensions multiprocess-compatible and then told them they'd have to throw that work away.
Re:Firefox 56: Last Stop Before Quantum by oblio on Friday October 06, 2017 @03:14PM (#15419557)
Notice how I carefully avoided your strawman. There were several reasons for their action. I listed what I believe are the 3 main reasons.
Re:Firefox 56: Last Stop Before Quantum by mook on Friday October 06, 2017 @12:17PM (#15417958)
They did have the choice to not ship the increased sandboxing, multi-process architecture and performance constraints until three months after the new extension APIs were ready. They didn't because they thought the trade-off wasn't worth it.
Re:Firefox 56: Last Stop Before Quantum by oblio on Friday October 06, 2017 @03:12PM (#15419540)
They really couldn't. People don't do things until pressured. Look what happened with Python 3. It took 10 years for it to reach Python 2 parity in terms of packages...
Re:Firefox 56: Last Stop Before Quantum by pseudalopex on Friday October 06, 2017 @06:08PM (#15420826)
The problem with WebExtensions has been Mozilla not providing APIs, not extension developers dragging their feet.
Re:Firefox 56: Last Stop Before Quantum by digi_owl on Friday October 06, 2017 @02:55PM (#15419386)
I really do miss the slow and methodical Mozilla that was not out to chase the latest Chrome fad...