3 ms·
They did have the choice to not ship the increased sandboxing, multi-process architecture and performance constraints until three months after the new extension
by mook 9y ago
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.
- 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.