5 ms·
I also hate they had to kill XUL addons, but they had good reasons to do so: https://yoric.github.io/post/why-did-mozilla-remove-xul-addons/ https://yoric.githu
by progval 5y ago
I also hate they had to kill XUL addons, but they had good reasons to do so: https://yoric.github.io/post/why-did-mozilla-remove-xul-addons/ https://yoric.github.io/post/why-did-mozilla-remove-xul-addo...
- chii 5y agoThose aren't good reasons from the user's perspective. Those reasons were good reasons from a technical, and maintenance perspective (which, as a software engineer, i understand). Those reasons are what engineers give to product management in order to get a green-field rewrite. But firefox's value add is their addon system - even if it is old, and difficult to use. It enabled some really great addons that weren't possible in the new replacement (as a simple example, the DownThemAll was rewritten using this new api, and it's shadow of their former self). Firefox should have paid the cost to maintain the old legacy system, and replace it only when the webextensions api is sufficient to replace _all_ functionality (which, of course, won't because webextensions evolved from google trying to kill off addons https://developer.chrome.com/docs/extensions/reference/ https://developer.chrome.com/docs/extensions/reference/ ).
- imbnwa 5y agoNot to mention XULRunner/XPCOM was Electron before Electron. I remember using the Songbird app, as well as an IM client whose name I can't recall now, across Windows and Linux back in the 00s. So They literally decided to cede the cross-platform browser-based desktop software framework du jour to Chromium.
- MomoXenosaga 5y agoWhen they explained it I actually agreed with the changes. But that was on the condition that those extensions would be coming back. But it's been years now and Mozilla's only solution is to switch to nightly.