Announcement
Collapse
No announcement yet.
Quantum-ized Firefox 57 Ready For Download
Collapse
X
-
Originally posted by JPFSanders View PostAnd with this Firefox will lose half its loyal base. The extension debacle is a fiasco of the highest magnitude.
Originally posted by Ropid View Post
This would also be a good time to check out Chromium as now there won't be a big difference between what type of extensions Firefox and Chromium can run. Without the old extensions, you are now free to give other browsers an honest try. There's nothing holding you back if you find out there's something to like about the other browser. With being free to choose other stuff, hopefully losing your old extensions won't be as bad as it feels at first.
- Likes 9
Comment
-
I guess I'll be sticking with FF 56 for a long time as my add-ons aren't support by FF 57. I'm not willing to sacrifice privacy and usability over some improvement in performance. "Some" in the way that I don't have to wait ages for pages to load now, so further improvement is not my main wish
Comment
-
Originally posted by Hibbelharry View PostThat step was really needed. Taking care of all that hassle never worked and slowed development really really down. Firefox needed a hard cut, and did just that.
Hey, lets break old addons with that multiprocess thing(?), then lets break them again by moving to a whole new API. And lets remove the old API before we implement the replacements!
Comment
-
Originally posted by AnonymousCoward View Post
They did it in a pretty bad way though:
Hey, lets break old addons with that multiprocess thing(?), then lets break them again by moving to a whole new API. And lets remove the old API before we implement the replacements!
Luckily the most used extensions were able to switch in time. I haven't lost any myself.
- Likes 4
Comment
-
Originally posted by Danielsan View PostFirefox gave a plenty of time to all the contributors to switch to the new API, imho.
Mozilla did *not* handle the transition correctly. They did not give enough time, some stuff isn't ready and there's too many API requests that have been denied.
- Likes 2
Comment
-
Originally posted by Gusar View PostConsidering some APis aren't even done yet (toolbar API and the ability to hide the tabbar, to name just two examples), no, they most certainly did not. Then there's APIs that they plain refuse to implement, like mouse tracking, which means gesture extensions have to resort to a really gross hack - inject tracking scripts into every page you visit.
Mozilla did *not* handle the transition correctly. They did not give enough time, some stuff isn't ready and there's too many API requests that have been denied.
- Likes 1
Comment
-
Originally posted by EarthMind View PostI guess I'll be sticking with FF 56 for a long time as my add-ons aren't support by FF 57. I'm not willing to sacrifice privacy and usability over some improvement in performance. "Some" in the way that I don't have to wait ages for pages to load now, so further improvement is not my main wish
(That's what I'm doing while I continue to find or write replacements for the extensions I need... in some cases, as native applications with an integration extension because the Firefox devs are reticent to support things like allowing a download manager arbitrary read/write access to a specified folder under the WebExtensions paradigm.)
- Likes 1
Comment
Comment