The "legacy" Firefox extension API is powerful because it reaches its tentacles into every corner of the internals of the browser. Keeping that API stable involves freezing a large amount of internal architecture and behavior.
Firefox needs to evolve if it's going to live, and it can't evolve in the ways that it needs to if so much of its internals are effectively frozen. It's a painful drag on development, slowing things down and preventing necessary changes.
I'm not even going to get into the problems with the API itself except to say that it had many, including widespread dependencies on synchronous behavior.
Mozilla's sacred-cow-level commitment to preserving legacy extension support is a big reason why Chrome beat Firefox on so many technical levels for so long. It ate up a ton of developer time, held off or killed critical architectural changes, was the cause of a lot of crashes, hangs, memory leaks, security problems... Thank goodness that's about to be over.
I'm sorry that you'll miss it but this is a really important step. Mozilla is doing a great job with WebExtensions, I suspect you'll be happy with how things shake out in the end.
Wouldn't it be better to offer a legacy addon API shim - old addons would still work even on new Firefox.
Look, I get it. You have your extensions and you don't want to see them go away. But you're a tiny niche and even other power users don't use these extensions that you find essential. Certainly the vast majority of users rarely install extensions at all. Mozilla is doing the right thing and an entire thread praising the performance of the latest version vindicates their approach.
Where is the next Servo based browser? Instead of refactoring the 20year old mess (with COM and XML), the should focus 99% on Rust and Servo, and finally release a stable build with a lightweight HTML5 UI (Vivaldi).
Well, you answered your own question. Clearly they have a userbase that will stay with them out of inertia or loyalty. These users can now benefit from the improvements in the latest release. If they released a new browser, few people if any would try it out because of inertia. The lack of users would kill the product pretty quickly.
Of course, some users who rely on old addons will be left behind, but they have the option to use Firefox Extended Support Release, which will get security updates. Eventually the extensions situation will sort itself out and these few users can move to the main release.
That's Firefox. Many of the components in Firefox 57 are taken from Servo.
You're in the minority then. The majority of users care, a lot, about speed, and Firefox is visibly slower than Chrome, probably one of the main reasons it has lost so much share.
Personally I care about both, that's why I am so conflicted about this update. But it's disingenuous to assume this is an unwarrented regression. You cannot get better in terms performance while keeping the extension system as it is. This reworking is necessary for Firefox to even compete wit Chrome. I understand the dillema but this is far from clear-cut one way or the other.
The majority of users care, a lot, about speed
Yeah. I care about browser speed a lot; I'm one of those guys always looking for settings to tweak and measuring results and so forth. I spent I-don't-even-want-to-know-how-many hours a week using a browser so even small improvements become noticeable quality-of-life upgrades.But, still:
1. Benchmarks are important, but aren't always the best reflection of actual performance, either real or perceived. Subjectively, Safari on Mac and Edge on Windows "feel" fastest to me even though benchmarks say otherwise. Within reason, that's what typical end users care about: "feel" vs. benchmarks. (FWIW, Firefox is my main browser; I'm not telling anybody to use Safari or Edge)
1a. Chrome benchmarks the best, but it also uses the most memory due to its multiprocess model, so for users on memory-constrained devices (particularly with spinning HDDs, where swap's going to be really slow) I'm not convinced reality always lines up with benchmarks here
2. The user's network connection is still usually the biggest factor.
3. I don't think actual site content's getting much heavier. All this extra browser performance is just getting soaked the hell up by heavier and heavier ads. So I can't get as excited about browser performance as I used to.
The added extensibility, while nice, was mostly an afterthought. The only extension I'll miss is cliget, and hopefully it can be added back eventually.
For instance neither "classic" top tabs nor a side list/tree is the "best" or "right" way to design a tab selector. Some users will prefer one, others the other. You should give them choice.
I think building support for a choice about something like tab placement is a waste of time and code - I don't understand why people can't adapt to one way or the other and then we all benefit from simpler code with fewer bugs.
I don't think we need to decide if top or side tabs are better, because I can't see how it matters much. Just pick one, hard code it, and everyone get on with the things that matter.
I spend several hours every day on a browser, switching tabs hundreds of times. I am measurably and subjectively more efficient with side tabs than top tabs. Why is this something that doesn't matter? It's not trivial, I literally cannot browse without side tabs without getting annoyed. It's absolutely not a waste of time and code if it's important to people.
Not really a "configurable option" but very close to it, it achieves the same goal and has been released along with the Backspace modification.
Just customize!
Not supporting images or JavaScript would simplify things as well...
That's just your opinion—which I guess the Firefox devs and most users don't share.
Customizability is a very useful feature for many people.
http://i.imgur.com/AH1ahF3.jpg
I really don't care which browser is #1 in speed tests. I don't care about integrations with social networks. I simply want a browser that I can configure the way I want!
Another suggestion : when you change something, even if you are 100% sure everybody will like it, please at least leave an "about:config" option that can revert that modification.
Sadly, I realized that, when Firefox is updated, I'm not trilled anymore to see what new features are included, I'm instead anxious to see what has been changed/removed!