3 ms·
Moving to Firefox 52 isn't really an option for me because it's a pig compared to 55/56 (it consumes almost 5GBs of RAM compared to 1GB for 56).
by shock 9y ago
Moving to Firefox 52 isn't really an option for me because it's a pig compared to 55/56 (it consumes almost 5GBs of RAM compared to 1GB for 56).
- sp332 9y agoI think you can switch to an unbranded build of 57, and enable legacy addons. https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Builds https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu... You could also install the Developer Edition or a Nightly build. They're slightly less stable (usually pretty good for me) but they have the same option. https://www.mozilla.org/en-US/firefox/channel/desktop/ https://www.mozilla.org/en-US/firefox/channel/desktop/
- sebazzz 9y ago> enable legacy addons Does that mean the XPCOM system has just been flagged as disabled, but not been removed yet?
- sp332 9y agoAs far as I know, yes. Firefox has already decided to transaction away from XUL, so the extensions will break eventually. It's just a question of when the particular APIs your extension relies on get removed.
- bzbarsky 9y agoVarious stuff has been removed. Other things have not been removed yet. You can see https://bugzilla.mozilla.org/showdependencytree.cgi?id=1347507&hide_resolved=1 https://bugzilla.mozilla.org/showdependencytree.cgi?id=13475... for a non-exhaustive list of things that can definitely be removed but haven't been yet.