3 ms·
the old APIs were actually the only existing, internal and synchronous APIs which does not work in a multi-process, site-isolation architecture. The internal A
by bugmen0t 4y ago
the old APIs were actually the only existing, internal and synchronous APIs which does not work in a multi-process, site-isolation architecture.
The internal APIs also had to go. What else would you do?
- noisem4ker 4y agoUnfortunately not many seem to remember that brief period when the old add-on APIs were being ported and made to work with a multi-process architecture, as part of the effort known as Electrolysis [1], with appreciable results, before being completely killed in favor of WebExtensions. I'm sure there were significant technical challenges, but let's not use these to hide the political reasons behind such a drastic move. [1] https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis
- bugmen0t 4y agoThese APIs were synchronous and thus blocking. People blamed Firefox being slow when in fact, it was mostly extension APIs and the extension code.
- sfink 4y agoElectrolysis was an easier thing to handle, and some APIs would still have been lost. Fission (process-per-origin) came later and would have broken many, many more. So people would have still been pissed off at Mozilla (the difference between levels of breakage would have been lost), and Mozilla would still be on the hook for supporting a barely supportable API. Without the resources that would require.