7 ms·
Why, with the ability to write powerful extensions removed it is basically a second Chrome now. I think WebExtensions were a good idea, but removing the raw ac
by kevincox 9y ago
Why, with the ability to write powerful extensions removed it is basically a second Chrome now.
I think WebExtensions were a good idea, but removing the raw access is removing what made Firefox great in the first place. Hopefully they will add an escape hatch in a future release but I'm not holding my breath. I wonder how long staying on nightly will allow "legacy" extensions.
But sure, a bit of performance is nice I guess.
- kevingadd 9y agoI hate WebExtensions, but Mozilla has at least demonstrated a commitment to improve and expand that API instead of letting it rot like Google has. They seem to be adding essential features to it so I think most of the good extensions will be possible within a few releases. I still wish they hadn't crammed it down our throats before it was ready, though. Jetpack extensions worked fine.
- Sylos 9y agoThey unfortunately sort of had to rush it. They needed to deprecate legacy extensions, because the majority of those are multiprocess-incompatible and they needed multiprocess to stop the bleeding of users. It's really quite visible, multiprocess was rolled out in Firefox 48 on the 2nd August 2016: https://www.netmarketshare.com/report.aspx?qprid=1&qpaf=&qpcustom=Firefox&qpcustomb=0&qpsp=202&qpnp=25&qptimeframe=M https://www.netmarketshare.com/report.aspx?qprid=1&qpaf=&qpc...
- s_kilk 9y ago>> but removing the raw access is removing what made Firefox great in the first place. The raw access is also what made Firefox slow and cumbersome compared to Chrome. The recent performance improvements would have been impossible with the legacy extension apis. Honesty I think this is a good move.
- kevincox 9y ago> The raw access is also what made Firefox slow and cumbersome compared to Chrome. The recent performance improvements would have been impossible with the legacy extension apis. This is simply not true as evidenced by the fact that Nightly still has the legacy extension API and the improved performance. That being said FF was slowing down to keep extensions compatible. This is why I think WebExtensions are a good idea. They should be the recomended path with promised future compatibility. Then FF can not worry as much about refactoring the internals as there are fewer extensions that would be broken and they "signed up" for it. I would rather have a faster FF and have to patch VimFX every couple of releases then have FF show down development for fear of breaking things. That being said loosing the extensions that gave FF it's magic is not a good tradeoff in my opinion.
- pitaj 9y agoThe legacy API is not on nightly. I think they have a similar API in WebExtension Experiments, but in nightly, legacy add-ons do not work.
- kevincox 9y agohttps://wiki.mozilla.org/Add-ons/Firefox57 https://wiki.mozilla.org/Add-ons/Firefox57 On nightly the extensions.legacy.enabled can be set to allow instalation of legacy extensions.
- jtgeibel 9y ago> To assist with performance analysis leading up Firefox 57, in Nightly only we are turning off add-ons that require shims. This was for pre-57 and doesn't apply to 57+.
- andrewshadura 9y agoThat isn't true, I'm running 58.0a1 nightly with legacy add-ons enabled.
- pferde 9y agoSo, I can't do what I need, but at least I can do what I don't need quickly. Yay progress!
- callahad 9y agoWebExtension Experiments are effectively that escape hatch. They have more or less the same access to the internal APIs as legacy add-ons, with the only restriction being that you can only install them on Nightly and Developer Edition. The intent is to have a way to prototype new WebExtension APIs (like hiding individual tabs, or the entire tab bar, or new theme APIs), but there's no requirement that they ever get merged upstream. You're welcome to build and distribute your own for whatever purpose you might want. https://webextensions-experiments.readthedocs.io/en/latest/ https://webextensions-experiments.readthedocs.io/en/latest/
- mtgx 9y agoThe old model is a security mess. Even WebExtensions doesn't seem immune to security issues: https://palant.de/2017/11/11/on-web-extensions-shortcomings-and-their-impact-on-add-on-security https://palant.de/2017/11/11/on-web-extensions-shortcomings-...
- kevincox 9y agoIf course it was. But there a couple of addons (for me just VimFX) that are going to require full control anyways. Also it seems to not have done much as basically every extension just asks for full access to every page, but I guess that some don't is an improvement.
- clouddrover 9y ago> Why, with the ability to write powerful extensions removed it is basically a second Chrome now. No. Firefox's WebExtensions API already offers more than Chrome's does (see webRequest as an example: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/API/webRequest https://developer.mozilla.org/en-US/Add-ons/WebExtensions/AP...) and more APIs will be added over time to enable more features.
- kevincox 9y agoWhile I'm glad they are offering more APIs there will always be a difference between what they decide to offer and basically everything.
- Sylos 9y agoMost legacy extensions should already be broken on Nightly, are they not? They've refactored tons of code under the hood, basically all the changes that they've wanted to do for years but couldn't do, because it would have broken too many extensions over and over. We're also talking about all the performance improvements that were made since Firefox 48. The majority of legacy extensions are not multiprocess-compatible and they would not have rolled out multiprocess in 48, if they wouldn't have known those multiprocess-incompatible extensions to be deprecated now with 57. Otherwise AMO would have basically been reverse Russian Roulette, where only roughly 1 out of 6 extensions will not kill your performance.
- kevincox 9y ago> Most legacy extensions should already be broken on Nightly, are they not? Yes, a lot would be. However if they could still be used many of them would have been fixed by now. > The majority of legacy extensions are not multiprocess-compatible Yet many are. My point is basically that I would like if FF supported the legacy "API" and left the community to manage fixing things that were broken. I would take this work over not being able to have some extensions any day.
- Sylos 9y agoI can understand your point of view, but I do think it is very much necessary to cut things off completely. Otherwise you'd have tons of extensions that could be rewritten as WebExtensions but aren't, because it's less work in the short-term to just fix them for the XUL changes. In the long-term, however, it would be a lot more work, especially if Mozilla starts recklessly breaking things. Similarly, many unmaintained extensions will disappear and WebExtensions will be written to replace them. Those will almost certainly have better quality and performance. Shouldn't be all too hard to pull off for an unmaintained extension. And then there's also stories like with NoScript's transition, which very much is a lot of work, but it will leave the NoScript maintainer with a much cleaner code base, not just from the WebExtension API being cleaner, but also simply because he rearchitectured the whole thing, as he was forced to rewrite anyways. And he'll get significantly better performance out of this, too. He would not have done a rewrite without this, but he's glad that he did it.