@forteller but they're killing a *lot* of extensions.
People who stopped using Firefox for speed will probably mostly stay on Chrome/Chromium; those who stayed on Firefox for the extensions now will have no reason to stay.
Sad, really.
@forteller ah, didn't know about Waterfox. Will give it a spin. Thank you!
@forteller @rysiek I understood a technical reason was that a misbehaving plugin using the old API could hang the whole browser.
@hjkl @forteller @rysiek From what I've heard, the technical reason is they want to be able to replace 2/3 of Firefox internals, including XUL, with parts from Servo, and there's no way to do this in a way that doesn't break XUL extensions.
@Wolf480pl @hjkl @forteller but but but... what about: chrome://browser/content/browser.xul
@rysiek @hjkl @forteller there will be browser.html ;)
@hjkl @forteller well, I *hope* it's for the best. Still, will give WaterFox a spin.
@rysiek I tihnk it's fantastic that Chrome extensionos will now be useable in Firefox! Less lock-in by "addiction" to third party ecosphere.
Though I don't know why they're killing support for the old extensions when it seems like forks like Waterfox are able to support both. https://www.waterfoxproject.org/