4 ms·
I use Firefox because of 2 things: 1) vimperator 2) single process handling multiple tabs (I typically have upwards of 40 tabs open at a time) Firefox is in t
by imron 10y ago
I use Firefox because of 2 things:
1) vimperator
2) single process handling multiple tabs (I typically have upwards of 40 tabs open at a time)
Firefox is in the process of removing plugins like 1) so that it makes it possible to remove 2).
Wonderful.
- Tree1993 10y agoIs there a way we can continue use these classic addon?
- richardboegli 10y agoPale Moon
- sychophant 10y agoThanks for the tip on this - installing.
- fuzzy2 10y agoHowever, that’s pretty much the other extreme. It doesn’t support Web Extensions or even Add-on SDK extensions.
- sychophant 10y agoDo you use any indispensable add-ons that are Web Extension based?
- fuzzy2 10y agoNo. However, I am the developer of "Download Cleaner", which is made using Add-on SDK. I think it's a great solution to get started without learning XUL. I'm sure they had their reasons for deciding what they did. I still think it's a bad decision.
- darklajid 10y agoYou can use the LTS (Extended Support Release? Not sure about the Mozilla terminology) version. For a while..
- hoschicz 10y agoIt's called Firefox ESR
- cpeterso 10y agoThe next Firefox ESR will be based on Firefox 52 (to be released in March). Firefox 52 ESR will continue to support all add-ons and receive security fixes until sometime in 2018 H1.
- jessaustin 10y agoIs there a Patreon for that?
- fabrice_d 10y agoAbout 2) : the multi-process model is not "1 process per tab", but "M tabs sharing N processes". So you won't end up with 40 processes in your case. I've been running nightly with 5 processes for months and found that to be a good setup.
- et1337 10y agoVimium on Chrome is pretty good.
- beerbaron23 10y agoIf you are a power tab user, there is no match, you have to use Firefox.
- buovjaga 10y agoSupport for vimperator-type things is coming: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061 https://bugzilla.mozilla.org/show_bug.cgi?id=1215061
- GraemeLion 10y agoFirefox is not removing those plugins. Vimperator has an issue in it's github referring to e10s and webextensions from 2015. It was commented upon a few times through 2015, more in 2016, and obviously more now. Nobody ever started moving forward. Only 10 days ago, a different issue was opened with regards to porting to an entirely new codebase for vimperator that uses WebExtension. They just now are talking about getting in touch with Mozilla for API requests. Mind you, a year plus ago, multiple mozilla developers were holding office hours blocked out in the day to explicitly talk to e10s and webextension developers. It got scaled back because nobody ever talked to them and paid developers cannot be paid to do nothing for hours at a time when nobody calls in/emails/etc. Meanwhile OTHER plugins HAVE taken this seriously, but not a lot of them. Certainly not enough. And yes, that means that you are going to have those plugins lose compatibility. But that's not firefox's fault. Mozilla has done everything they can do to help this transition, including paying people to help, pushing it back multiple times, giving numerous conferences, opening up api requests, and communicating on most every forum available on the internet. It's on the plugin developers now. That's where your anger should be. Not on the company that is doing, finally, what it said it'd do numerous years ago.
- imron 10y agoThanks for the detailed response. As someone who doesn't follow the nitty-gritty of Firefox development, it's frustrating to only really find out about it when things stop working.