3 ms·
It's because of the killer combo of increased sandboxing, multi-process architecture and performance constraints. I think they couldn't keep everything togethe
by oblio 9y ago
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.
- mook 9y agoThey 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.
- digi_owl 9y agoI really do miss the slow and methodical Mozilla that was not out to chase the latest Chrome fad...
- oblio 9y agoThey 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...
- pseudalopex 9y agoThe problem with WebExtensions has been Mozilla not providing APIs, not extension developers dragging their feet.
- pseudalopex 9y agoMultiprocess 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.
- oblio 9y agoNotice how I carefully avoided your strawman. There were several reasons for their action. I listed what I believe are the 3 main reasons.