No, security threats make both developers and users worse off.
It's undoubtedly true that power users will lose a little of the functionality they like in Firefox, but that normal users will have a more secure browser. I'm sure someone will fork Firefox to keep a version alive for those power users.
You might not agree with it, but the logic is sound.
> It's undoubtedly true that power users will lose a little of the functionality they like in Firefox, but that normal users will have a more secure browser
Why are these 'normal users' going to use Firefox when their power user friend no longer recommend it, when Google is pushing Chrome as hard as they can on every Google property, and when there are even installers that 'offer' to install Chrome for you? Mozilla can't compete with Google and Microsoft marketing efforts, they can't make anything more than a UI for the most popular mobile browsing platform, and they're alienating power users. Who is going to be pushing Firefox to normal users?
So, fix the problem instead of throwing the baby out with the bathwater.
I get it, it's a hard problem to fix. There would be a lot of pain in getting there, both for Mozilla and addon developers. But throwing in the towel feels like a cop-out.
The logic is sound, but so is closing down every theater because someone got shot in one of them. After all, everyone has TVs and blu-ray players now, and you can't get shot in a theater if there are no theaters...
But this is the fix. Instead of allowing open access to the internals of Firefox, which will never be secure, you use a limited API. It isn't difficult to imagine that they can expand this API later to allow things that aren't currently possible. It's a hard problem to fix and there will be pain getting there.
And the theatre analogy is just silly. It's not like shutting down a theatre because someone got shot in it, it's like enacting a "no guns in this theatre" policy instead.
This is a fix. It's not the only fix. I postulate that it's probably not even the best fix for Firefox.
> Instead of allowing open access to the internals of Firefox, which will never be secure
Android, iOS, and many other OSes do this all the time via rather granular ACLs. It can be done.
All analogies are flawed - but Firefox is closing the theaters by completely killing off their add-on interface in exchange for an comparatively shallow experience.
> Android, iOS, and many other OSes do this all the time via rather granular ACLs.
If it were that simple, then the Chrome team would simply have asked the Android team to provide their expertise in designing Chrome's extension API. And of course, it's not like Android provides apps unrestricted access to the hardware (there's a reason that people bother to root their phones). Firefox addons are currently less restricted than Android apps.
> the Chrome team would simply have asked the Android team to provide their expertise in designing Chrome's extension API
Chrome's choice to not use such ACLs has no bearing on whether it is possible or reasonable for a web browser to use. Chrome is not the be-all-end-all of browser technology.
> Firefox addons are currently less restricted than Android apps.
And that's what could be changed. The lack of restrictions in the current state doesn't mean that it can't (or that it shouldn't) change.
It's undoubtedly true that power users will lose a little of the functionality they like in Firefox, but that normal users will have a more secure browser. I'm sure someone will fork Firefox to keep a version alive for those power users.
You might not agree with it, but the logic is sound.