It breaks about 2/3 of the extensions I was using, and many of them don't currently have similar replacements available. That's a big loss in some of the functionality that made Firefox attractive as my default browser.
I understand the desire to fix fundamental architectural limitations. In the medium term some of those extensions will probably be updated or replaced. In the long term, the improvements may well pay off in terms of better security and better performance and easier development allowing faster progress. As a software developer I can see that the move was rational even if it is also somewhat controversial.
But in the short term, the loss is still significant for some users. That's a perfectly legitimate concern, and it's apparently sufficient that some people are not upgrading this time.
I tried to think forward, and proactively convert my greasemonkey scripts to new style FF extensions a few months back, to avoid dependency on GM. But abandoned that after it became clear that I'm not allowed to install my own extensions on regular Firefox, because of forced thir-party signing requirement. I have no need for signing. I could create an extension by zipping a directory. Now the workflow is 1000x more complex with all the crap loaded from npm required to sign it.
My web experience is s*it, ATM.
Firefox is great anyway. But it is power user hostile in some aspects too. Personal extensions/userscripts are central to my use of the web. So this is all quite annoying, since signing was enforced. And now even my userscripts broke with 57, as expected.
To all those claiming that Mozilla doesn't owe this to their users, you are technically correct. But why piss off users when you can easily satisfy them with a simple option. I shouldn't have to use a patched browser for something so basic.
I think that the issue was that they were worried about people who don't understand the security implications turning verification off and getting themselves into trouble.
> It's my computer, not Mozilla's.
Then you'll be overjoyed to hear about the unbranded builds! The exact same code, except it's yours, so it allows all extensions and doesn't say "Firefox" on it.
But Mozilla doesn‘t owe every single user his own build with their pet features.
Sorry to hear this; but I think it's arguably more important for Mozilla to improve the web experience for a hundred million users who may never "write userscripts / extensions" for any website than to hamstring their development in order to avoid inconvenience to a single user who feels the need to customize every point of their web experience.
Also mandatory signing doesn't improve web experience for anyone. It's a security feature. Security is always inconvenient, almost by definition. So your point is invalid.
I don't mind change, I like new Firefox features, what I dislike is imposition of stupid lockdowns, and pointless control. One valid point, I might concede, is that there are innocent third parties affected if someone clueless confirms installation of some malevolent extension. So restricting it is somewhat justified.
Anyway, it's all still a sham. Anyone can still disable mandatory signing with a simple 10 line script patching omni.ja in any Firefox. So it's still no security against people who can be persuaded to enbale something in about:config, or run firefox with a command switch, or add some file to /etc/firefox/, or run a simple 10 line script "to make firfox compatible with our great extension".
1. Video performance. Even something as simple as opening a video in reddit spikes my CPU to 100%, and before reluctantly installing Adblock Plus I ran into multiple kernel panics from opening articles on mainstream news sites and blogs.
2. Pinch-to-zoom isn't supported (closest alternative I could find is some about:config settings to make the pinch gesture equivalent to cmd++/-, which isn't useful).
I'm still using Firefox, and there's a lot that I like about it more than Chrome, but I'm seriously considering switching back because of those and some other minor issues.
At one point the whole browser crashed. So right now got Chrome and FF open and am switching depending on the site. Might just end up back in Chrome if this isn't resolved.
Is it that easy to panic the macOS kernel?
FF57 is absolutely the greatest version of Firefox to date. I have yet to hear a single legitimate complaint against it that actually holds up to scrutiny.