News for hackers. Stuff that matters.
Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @03:16PM (#15157716)
Dear Mozilla developers! I've been using Firefox since v1.0. And I want you to know that by ditching the old plugin architecture you are alienating your faithful users, myself included.

I'm sorry, but I decided to stick with Firefox 55 for now, possibly switching to Palemoon later. I need my old extensions to work: Status4Evar, EdgeWise and Classic Theme Restorer. I can't stand the current FF UI and I will not give up on this.

Re:How you can contribute to Firefox 57 success by JohnBooty on Saturday September 02, 2017 @05:51PM (#15158412)
While we're throwing anecdotal statements around...

Dear Mozilla developers!

I've been using Firefox as my daily driver nearly non-stop since it was Phoenix and I'm totally cool with you dropping the legacy stuff.

Re:How you can contribute to Firefox 57 success by joneil on Saturday September 02, 2017 @08:40PM (#15159053)
I'm the same. Been using since Phoenix 0.3 and am stoked about these changes, and the thought that Rust, and the major perf and safety improvements that come with it, are beginning to find their way into Gecko. Amazing work from a team that many had dismissed as irrelevant.

Prove them wrong!

Re:How you can contribute to Firefox 57 success by chrismorgan on Sunday September 03, 2017 @10:03AM (#15161454)
Dear Firefox developers,

I’ve been using Firefox as my standard browser since 0.9.3 (except for a year or so when it was run-a-browser-from-a-USB-disk-or-use-IE and Firefox was just too terribly slow, so I used Chrome—by the next year Firefox had fixed its game and I could switch back), and for the last few years Nightly has been my standard browser.

I get why you’re dropping the legacy stuff and I’m looking forward to what’s possible after it’s gone. When the announcement came out in November last year that WebExtensions would be the only way come 57, I was intensely sceptical that it’d be ready within a year (no one was using it at that time) and prepared for a deal of pain: I’d just have to live with it, come November. (It’s not like I have any better options in mainstream browsers; they’re all hopeless with even only twenty tabs.)

Well.

You’ve proven me wrong, and I’m delighted. I was able to replace all my legacy extensions with WebExtensions ones with minimal loss of functionality (I miss the ability to style the chrome with Stylish, not that I was actually using it for anything other than shaving half pixels off here and there on my high-DPI screen). My Dad (also a programmer) is still grumbling about some status bar thing that broke a short while ago, but we went through his extensions and came to the conclusion that it’s really not that bad—the extensions that stop working at 57 were ones he didn’t use, or ones where there are already good alternatives available or a clear plan for the changeover.

(The fact that in several cases I did have to swap out one extension for another was a mild nuisance, but as a Nightly user I’m doing this a few months before everyone will have to, so I expected it.)

All in all, I’m happy with how things have gone and impressed at how well the migration is going. All that I really want now is to be able to hide the horizontal tab strip in favour of my vertical tab bar. And it looks like https://bugzilla.mozilla.org/show_bug.cgi?id=1332447 is almost there. (It’d also be good if file: URLs didn’t mess with said vertical tab bar something awful, but as I haven’t filed any bugs about that yet or investigated to find existing reports I’m not allowed to complain.)

Good job!

Re:How you can contribute to Firefox 57 success by rnhmjoj on Saturday September 02, 2017 @09:43PM (#15159242)
I'm totally cool with dropping legacy stuff that has a proper replacement.
Re:How you can contribute to Firefox 57 success by Sylos on Sunday September 03, 2017 @01:12AM (#15159794)
Then you must hate all of your software. It's impossible to always continue in the direction that happened to be chosen more than a decade ago. At some point, you will run into problems, which in the case of Firefox were severe problems in performance, security, maintainability and complexity as well as stability of the extension API. You can't fix all of these problems without breaking things, without doing things differently.

And yes, it is to some degree subjective whether this is worth it, but at the end of the day, you, as someone who uses lots of extensions and complex extensions, are only a very small fraction of the Firefox user base. Most users have no extensions or just the obligatory ad blocker. They don't benefit at all from keeping onto the old architecture with all of its problems, which they are suffering under.

And then, yeah, Mozilla has to at some point piss you off in order to help the majority of their user base. It's not like all other browsers had such a complex extension API and Mozilla is just being lazy by dropping it.

Re:How you can contribute to Firefox 57 success by JohnTHaller on Saturday September 02, 2017 @06:18PM (#15158517)
Dear niche community using legacy extensions: We're sorry, but legacy extensions are holding back Firefox development in every way meaningful to the vast majority of users. In order to continue to exist as a viable option for an open web, Firefox must move forward. - (What I imagine they'd say)

Of the extensions you listed, the largest (Classic Theme Restorer) is only used by 333,000 people while the smallest (Edgewise) is only used by 218 people.

Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @09:53PM (#15159275)
Your arguments may convince Mozilla not to port these features to WebExtensions, but what are you trying to tell me? To go fuck myself? What you're missing is there are many niches like these, and many people using many niches. It might still be a small percentage of users overall, but we're the geeks and we sit right in the center of the culture. Get rid of us, and the care-about-Mozilla temperature goes down significantly.

Mozilla should find a way of moving forward while keeping the code open enough to modding. AFAIK, features offered by these extensions that I use are not implementable in WebExtensions even in principle, and that is the main problem. Break the compatibility if you must, but make it possible for someone who cares enough to step in and rewrite these extensions to the new architecture.

Re:How you can contribute to Firefox 57 success by JohnTHaller on Monday September 04, 2017 @11:59AM (#15169042)
The vast majority of Firefox users either don't use extensions or only use an ad blocker. I downsized to the same myself quite a while ago for performance and stability reasons in Firefox despite being one of the niche users that used to keep 10 extensions installed. Yes, there are quite a few different niches of users that use specific legacy extensions. But the legacy extension system is a mess and has been holding Firefox back for a while. Mozilla is going to fully embrace WebExtensions and keep moving it forward to enable as much functionality from old extensions as possible to serve several of those niches.

I'd argue that many of the users that choose Firefox over Chrome do so for the fact that Firefox is 100% open source and isn't tied to an advertising giant trying to capture tons of extra private data from you. This won't change that. It will mean you can't change the layout of the entire Firefox window and add tons of new custom buttons and things like that. But most users don't care about that.

For the niche that can't stand using a UI they can't fully customize, they're free to use a slower and less secure browser that continues to support XUL and the associated extensions while still keeping up to date with at least the slower Firefox ESR branch of renderer underneath. Pale Moon, for example.

Re:How you can contribute to Firefox 57 success by kirillkh on Tuesday September 05, 2017 @08:51PM (#15180318)
Legacy extension system vs WebExtentions is actually a false dichotomy. Mozilla still can develop a low-level API in front of its new and improved subsystems. Yes, that will require more development and will be harder to maintain. But the benefits it would bring may arguably be worth it.
Re:How you can contribute to Firefox 57 success by JohnTHaller on Friday September 08, 2017 @12:29PM (#15201621)
Mozilla is already planning on extension WebExtensions beyond what Chrome does with it (I believe they even implemented some of it already) and are planning on adding even more to enable the functionality of some of the more popular legacy extensions (bookmark trees, tab management, etc).
Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 09, 2017 @11:22AM (#15207492)
There is an umbrella issue that aggregates proposed improvements to WebExtensions [1]. If you look at RESOLVED WONTFIX issues linked in that bug, you will find a lot of them are rejected based on political reasons. For example: [2]. So there will never be anything close to feature parity with XUL extensions.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1215059

[2] https://bugzilla.mozilla.org/show_bug.cgi?id=1246706

Re:How you can contribute to Firefox 57 success by wtallis on Saturday September 02, 2017 @10:50PM (#15159441)
For every user of Classic Theme Restorer, there are probably a dozen more Firefox users who complain about the unnecessary UI changes but aren't aware that CTR exists to fix some of the usability regressions.
Re:How you can contribute to Firefox 57 success by lucb1e on Saturday September 02, 2017 @06:41PM (#15158615)
> only used by 333,000 people

doesn't sound like an "only" to me.

Re:How you can contribute to Firefox 57 success by JohnTHaller on Saturday September 02, 2017 @07:11PM (#15158746)
Firefox has 80 million daily active users, so that's an 'only' in context. Keeping XUL around and all of its messiness to support a small niche of users at the expense of what most users want is part of why Firefox has lost so many users to less customizable, (arguably) less capable competing browsers.
Re:How you can contribute to Firefox 57 success by throwaway2048 on Saturday September 02, 2017 @09:25PM (#15159181)
There are a boatload of assumptions in that statement that are pretty unwarrented. The vast majority of why chrome is popular is because google.com and youtube.com push it nonstop, not any other imagined reasons.
Re:How you can contribute to Firefox 57 success by Grue3 on Sunday September 03, 2017 @05:27AM (#15160486)
You're forgetting that people who want to use the features older versions had but not anymore are likely the same people who have been using Firefox for a long time. These are the same people who drive Firefox adoption by being experienced long-time users giving advice to the young'uns. If you lose that core user base, you'll lose the rest of 80 million to Google/Microsoft ads in no time.
Re:How you can contribute to Firefox 57 success by Max_Mustermann on Monday September 04, 2017 @12:22PM (#15169199)
likely _some_ of the same people..

Plenty of those long-time users giving advice to the young-uns are more than happy yo sacrifice a small part of firefox for big improvements elsewhere.

Re:How you can contribute to Firefox 57 success by zanny on Saturday September 02, 2017 @05:36PM (#15158343)
I've been using Firefox since 1.5, and I understand completely why they have to drop their legacy extensions framework to modernize the browser. In recent years I found myself using Chromium more and more because of its responsiveness. Firefox 57 is really close to where it needs to be to let me drop all my use cases of Chromium I have now. Yes, it means 4 of the ~12 extensions I've used for years stop working. Most of those have a web extension version being worked on or aren't worth the competitive disadvantage of supporting a 15 year old addon API.

I've seen plenty of my favorite software projects have to make "hard breaks" to modernize. KDE broke everything with Qt5 / Plasma 5, but the payoff is now they are the premier high DPI Linux desktop. Python broke everything with 3, but features enabled by the changes have made Python 3 the best scripting language ever in my book.

Firefox would be doomed to a slow death with its legacy extensions API the same way PHP and Perl languished for years with the inability to push a major version. A slow death is not a downfall anyone wants.

Re:How you can contribute to Firefox 57 success by catdog on Saturday September 02, 2017 @11:32PM (#15159541)
The issue is not that things break, the issue is that the WebExtensions API is missing a lot of features so a lot of addons can't be ported.
Re:How you can contribute to Firefox 57 success by JohnBooty on Sunday September 03, 2017 @02:22AM (#15159976)
It's missing functionality because the old API allowed deep, deep hooks into FF's internals.

Per Mozilla, aside from security problems and other nightmares, these deep hooks allowed developers to write plugins that were incompatible with a multiprocess browser architecture where each tab/window can have its own sandbox and remain responsive even if other tabs go down.

And that is one of the killer features that has caused FF to bleed massive amounts of user share to Chrome in the last decade: Chrome almost always "felt fast" in situations where FF ground to an embarassing halt because something was happening in another tab/window that was causing the entire browser to become unresponsive.

I don't know what precisely is missing from the new WebExtensions API but I have to imagine that Mozilla will work to expand its capabilities as much as possible over time...

Re:How you can contribute to Firefox 57 success by pseudalopex on Thursday September 07, 2017 @06:54AM (#15190605)
WebExtensions is also missing functionality because Mozilla set a release date before figuring out what APIs would be needed or how migration would work.

The Add-on SDK was supposed to fix the "deep hooks" problem and is mostly multiprocess-compatible. As far as I know, most currently maintained XUL extensions are multiprocess-compatible, too.

Re:How you can contribute to Firefox 57 success by dbolgheroni on Saturday September 02, 2017 @05:25PM (#15158293)
I rely mainly on one add-on: Vimperator. It's a big big productivity enhancer and it's the main reason for sticking with Firefox for so long. Even in a period when Firefox was slower and buggier than the alternatives.

It's sad they will deprecate the old extension interface and make Vimperator a no-no. I understand the reasons behind WebExtensions, specially those related to security, and reckon the benefits of the multiprocess paradigm, but the flexibility of the old extensions API was a big advantage in my pov.

No, Vimperator won't be ported (I wish it could), because WebExtensions is a much more limited API. And no, Vimium and VimFx doesn't come even close to it. They are not alternatives.

Re:How you can contribute to Firefox 57 success by NotOscarWilde on Saturday September 02, 2017 @05:32PM (#15158320)
I hate to add so little to the discussion, but I am on the exact same boat, and I am quite anxious about the upcoming change.

If there is anything to make either Mozilla hear this use case more, or contribute anywhere to make Vimperator a possibility for the future, I would be happy to do my part.

Re:How you can contribute to Firefox 57 success by weaksauce on Saturday September 02, 2017 @05:47PM (#15158396)
fwiw they seem to be actively trying to support vimperator like webextensions in this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1215061

What does vimperator do that vimium and vimfx can't?

Re:How you can contribute to Firefox 57 success by kronos29296 on Saturday September 02, 2017 @06:02PM (#15158458)
Though I haven't used it, it seems to radically make firefox into something like Qutebrowser. Not just the key bindings but also the UI which is not possible under new api for Web extensions while Vimium and vimfx only give vim key bindings in the browser (Not the full experience for those who are used to vimperator).
Re:How you can contribute to Firefox 57 success by maxerickson on Saturday September 02, 2017 @04:52PM (#15158147)
I've been using Firefox since ~Phoenix 0.1 and I don't care at all about the legacy plugins.

It would be interesting to see what percentage of their long time users use more than 1 or 2 add ons (I have 4 installed and only really use 2 of them).

Re:How you can contribute to Firefox 57 success by wvenable on Sunday September 03, 2017 @02:04AM (#15159927)
In my case, the critical extension for me is Tab Mix plus (770k users) for multi-row tabs. It's really hard to use a browser without this feature because I've been using it for so long.

The real question is for me is how many users haven't moved onto Chrome -- which is obviously faster and more stable -- because of 1 or 2 add-ons.

Re:How you can contribute to Firefox 57 success by contras1970 on Sunday September 03, 2017 @05:36PM (#15164060)
i've used ff since the phoenix days (0.6? do not remember). this particular laptop now has 55.0.2 with Cookie Monster, HTTPS Everywhere, NoScript, Policeman, Show my Password, Tab Mix Plus. some other extensions are installed but not used.
Re:How you can contribute to Firefox 57 success by throwaway2048 on Saturday September 02, 2017 @05:02PM (#15158194)
How many of those users really care about firefox and dont just use it for inertia reasons? (already installed, etc)

Frankly if they arnt using extensions they are going to have a vastly better user experience on chrome, and google has infinity manpower to always ensure thats the case.

So what is firefox gaining by becomming a crappier chrome? Why the hell wouldnt I just use chrome at that point, because I feel so great about mozilla, who regularly brushes me off when i try to take advantage of things unique to firefox?

Re:How you can contribute to Firefox 57 success by kronos29296 on Saturday September 02, 2017 @06:06PM (#15158470)
I use mozilla nowadays on my low end laptop because chrome chokes on it most of the time (just plain hangs and stops working with more than 10 tabs which is all the time for me). FF 55 is much snappier with most of my important extensions and doesn't choke as much. So I moved from chrome to FF after 55. Hope they continue to make it better.

P.S FF is now not a crappier version of Chrome but Chrome is crappier if you don't have powerful hardware or RAM (mine's hardly 2 GB and everything sucks a lot though its only 4 years old)

Re:How you can contribute to Firefox 57 success by 51Cards on Saturday September 02, 2017 @03:45PM (#15157837)
One more voice for the above. I will be stopping at Firefox 56 until I decide what works best for me. I rely on several plugins daily that are about to be made obsolete. Likewise I revert Firefox back to a very classic UI interface that is very compact and familiar. I have avoided Chrome all these years because I can't stand its UI. Now I'm also about to loose the ability to make FF feel familiar along with many of my required productivity add-ons.

I'll ride out FF 56 until I decide where to go next but honestly the many times in the past it has felt FF has ignored the requests of long term users, coupled with lack of differentiation from Chrome, I'm not sure I have much reason to stick around.

Kudos to the team for all the hard work improving the FF core. But you're about to abandon that which kept long term users like myself here through all those rough years. Makes me sad.

Re:How you can contribute to Firefox 57 success by SAI_Peregrinus on Saturday September 02, 2017 @04:18PM (#15157982)
I'm going to be switching to the extended support release[1] (based on Firefox 52 but with security patches through June 18th 2018).

I don't mind WebExtensions, and cross-browser compatibility is a nice goal, but a half-baked system that breaks the most important distinguishing feature of Firefox (extensions that can modify any part of the browser) is ridiculous.

[1] https://www.mozilla.org/en-US/firefox/organizations/all/

Re:How you can contribute to Firefox 57 success by Elhana on Saturday September 02, 2017 @05:19PM (#15158265)
I'm already on ESR, but my reason is I need java plugin for my company OEBS (it supports web start, but it takes ages for our admins to patch anything). At the same time, keeping legacy plugins working is a big bonus, I love Classic theme restorer.

Still undecided what to do after june 2018. I guess I'll just try firefox and chrome side by side and move to chrome if there is no real difference. It is probably more convinient to migrate to chrome, since it is on the phone by default too.

Re:How you can contribute to Firefox 57 success by romanovcode on Saturday September 02, 2017 @03:58PM (#15157886)
I don't agree.

Yes it's a change but it serves a good purpose - to standardize the extension development and making sure that 1 extension can be running on multiples browsers e.g. Firefox, Opera, Edge, etc..

Re:How you can contribute to Firefox 57 success by drdaeman on Saturday September 02, 2017 @04:03PM (#15157908)
WebExtensions is the lowest common denominator.

Yes, it's a good purpose to have a standard base. It's bad, though, that nothing besides the blessed parts are officially customizable anymore.

Previously, extensions had messed up with anything they wanted (they could override most of the browser's core). That had allowed third parties to do incredible things that weren't ever considered by the browser developers.

With WEs, though, the only things that browser developers had specifically thought about are possible. All for user's convenience, so they can switch to Chrome, Edge or Opera.

Re:How you can contribute to Firefox 57 success by cookiecaper on Saturday September 02, 2017 @05:24PM (#15158289)
It's the same thing as plugins, unsigned drivers, etc. etc. If the platform gives unfettered control, that is nice in that it gives power users flexibility, but it comes at the cost of seriously jeopardizing the experience of non-power-users who don't understand the intricacies of the software. They expect the platform to protect them by default. This applies to the whole package -- security, performance, and overall experience.

Vendors have learned that if they fail to provide this protection, the average user will blame them directly, not the extension that makes memory usage bloat 6x. The solution is to enforce stringent controls, including limiting modifiable parts of the experience to some well-defined areas.

Re:How you can contribute to Firefox 57 success by JBiserkov on Saturday September 02, 2017 @05:43PM (#15158368)
>All for user's convenience, so they can switch to Chrome, Edge or Opera.

Nah, it's the other way(s) around - it's for [longterm] developer convenience; so users don't have to switch to another browser because an add-on they need isn't available in FF.

Re:How you can contribute to Firefox 57 success by 51Cards on Saturday September 02, 2017 @06:38PM (#15158600)
Unfortunately I don't think so. The only draw keeping FF alive for years has been its extension system. They gave up the unique UI flexibility, now they are giving up the flexible extensions. When Google makes it so easy to find and install Chrome everywhere, and sync it with your mobile device, now that the extensions world will be on "par" FF is even less distinct than it was and thus less reason to use it. This is the beginning of Firefox's final dive.

In a few more releases I really won't have any concrete reason to recommend FF over Chrome anymore (and no, 99% of users outside of this forum don't care about memory usage and keeping 100 tabs open at the same time)

Re:How you can contribute to Firefox 57 success by drdaeman on Saturday September 02, 2017 @06:12PM (#15158494)
This too, but to the lesser extent. That's because Firefox had much more powerful extension system than other browsers.
Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @04:05PM (#15157921)
Then they should bring back the old UI we came to love. I want my blue title bar on Windows, my menu bar, my status bar, my square tabs, etc, etc. Also, I can't imagine living without EdgeWise, so they would have to incorporate that, as well. Other people use different sets of features, which are also not supported in the new plugin model. How can Mozilla ever hope to plug all these holes (pun intended)?
Re:How you can contribute to Firefox 57 success by mintplant on Saturday September 02, 2017 @06:46PM (#15158634)
> I want my blue title bar on Windows, my menu bar, my status bar, my square tabs, etc, etc.

So like this [0]? The title bar isn't blue, but neither is any other title bar on Windows 10.

To achieve this on Nightly I opened the Customize view, switched the theme to "Light", checked the "Title bar" checkbox, and enabled "Menu bar" under the "Toolbars" dropdown. Tabs have squared edges by default.

[0] https://vgy.me/KvNgxS.png

Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @09:42PM (#15159238)
No, like this: https://vgy.me/VBLBYH.jpg And when the FF window is not focused, the title bar is grey. Like it's supposed to be.

It's not part of a plugin, though, I had to patch something manually (I never remember what and have to re-google it every time).

Re:How you can contribute to Firefox 57 success by kronos29296 on Saturday September 02, 2017 @06:08PM (#15158479)
You get square tabs in 57 i think.
Re:How you can contribute to Firefox 57 success by clouddrover on Sunday September 03, 2017 @12:28AM (#15159699)
> my square tabs

Square tabs have been back for a while now. The Compact Light and Compact Dark themes are included in Firefox by default. Set the theme in Add-ons Manager -> Appearance.

I use Compact Light.

Re:How you can contribute to Firefox 57 success by drdaeman on Saturday September 02, 2017 @03:59PM (#15157889)
Actually, it still does support legacy extensions and probably will do for a while. There are `browser/features/*.xpi` files in the browser install directory. Even in 57, they're all "legacy" extensions, and the only WebExtension there is `[email protected]` (even then, still a "legacy" install.rdf-type file, with embedded WE).

And I've just copied the legacy `[email protected]` non-WE addon there - and it worked ;)

I'm sure they're going to plug this "hole" shut, but it's still there. As well as patching omni.ja.

Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @04:11PM (#15157950)
If it keeps working in FF 57 and won't break after every minor update, I might upgrade. I was actually thinking that providing some kind of officially unsupported backdoor for determined users like us might be a way out of this situation.
Re:How you can contribute to Firefox 57 success by Sylos on Sunday September 03, 2017 @02:08AM (#15159940)
No, it is going to break after every minor update. Most legacy extensions already don't work anymore in Firefox Nightly, even if you tell it to load them [0], simply because Mozilla has very much already used their new freedom to throw out tons of legacy code [1] and to refactor what's left.

The Mozilla-supplied legacy extensions continue to function, because Mozilla is updating them as they make changes to the internals of Firefox. So, I imagine maintaining such a legacy extension is now as much work as it is to just directly contribute and maintain the feature in Firefox's codebase.

[0]: "extensions.legacy.enabled" in about:config. This won't be shipped in Stable, though, and will likely be taken out from Firefox Nightly soon or with the release of Firefox 57.

[1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1347507

Re:How you can contribute to Firefox 57 success by majewsky on Saturday September 02, 2017 @04:30PM (#15158036)
I'm not involved in FF development, but I find it exceedingly unlikely that this will keep working for much longer than a few releases after 57. The whole purpose of all of this is to rip out all the XUL baggage to decrease maintenance cost and make it easier for the developers to focus on actual features and fixing bugs that actual people encounter (as opposed to keeping legacy code paths working where no one has a clue if they are even used anymore).
Re:How you can contribute to Firefox 57 success by drdaeman on Saturday September 02, 2017 @06:08PM (#15158480)
Ripping out XUL baggage is fine, it doesn't matter which language UI elements are described in. Yes, it would require to rewrite stuff, but that's manageable.

The important part is ability to replace (overlay) chrome resources, patching/extending the browser code. I hope that's going to stay for a while.

Re:How you can contribute to Firefox 57 success by drdaeman on Saturday September 02, 2017 @04:26PM (#15158019)
The internal APIs will eventually change (break). They already did on major releases - one can find lots of "does not work on Firefox NN+ anymore, please update" comments all over AMO. (By design, this should be significantly rarer occasion with the WebExtensions)

Now there is no requirement to keep them stable even across the patch-level releases. Whenever things would break faster or at the same pace is unknown.

Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @04:54PM (#15158157)
I know it's not a good way out, but it's something we could at least in theory work with.
Re:How you can contribute to Firefox 57 success by michel-slm on Saturday September 02, 2017 @07:45PM (#15158877)
I used to do that until I discovered the Compact theme (which is now installed by default, previously only available on the developer edition without installing an add-on).
Re:How you can contribute to Firefox 57 success by endemic on Saturday September 02, 2017 @09:04PM (#15159123)
Love the compact theme. Glad it made its way into the release channel.
Re:How you can contribute to Firefox 57 success by jccalhoun on Saturday September 02, 2017 @10:45PM (#15159424)
I've been using firefox since the very early days and I am excited about ditching the old plugin architecture.

Oh, and good news, the ui you dislike is going away.

Re:How you can contribute to Firefox 57 success by klondike_ on Saturday September 02, 2017 @04:34PM (#15158060)
The main problem with legacy extensions is that they won't work with multiprocess firefox by design. Multiprocess is the only way forward, because of the enormous speed and stability benefits.

Unfortunately Mozilla has rushed the transition, and there hasn't been enough time to add important APIs and for developers to update their extensions. Firefox 57 is on the verge of being released, and there are still many addons which aren't webextension compatible.

Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @04:48PM (#15158121)
Isn't v55 already multiprocess? How are these extensions working right now?
Re:How you can contribute to Firefox 57 success by johnny22 on Saturday September 02, 2017 @06:41PM (#15158617)
many of the apis were shimmed in such a way so that they'd work, but could still slow down the browser. Those shims will disappear.
Re:How you can contribute to Firefox 57 success by zanny on Saturday September 02, 2017 @05:33PM (#15158322)
If you have any legacy extensions installed multiprocess is disabled. If you don't have any, it is turned on.
Re:How you can contribute to Firefox 57 success by scott_karana on Saturday September 02, 2017 @06:41PM (#15158613)
Not correct. Some legacy plugins work fine: the add-ins store relied on user testing and flagging to confirm which still worked.

https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/Multi...

Re:How you can contribute to Firefox 57 success by clouddrover on Sunday September 03, 2017 @12:07AM (#15159645)
> I can't stand the current FF UI and I will not give up on this.

Then the simple way forward is to make your own browser, isn't it? Use an embeddable engine which does all the hard work for you and focus on making the UI the way you insist it must be. It really could be a single developer project.

So why not just do that?

Re:How you can contribute to Firefox 57 success by ramshanker on Saturday September 02, 2017 @04:07PM (#15157928)
>>alienating your faithful users, myself included.<<

I wonder what the telemetry says about those plugins. If it shows a minority, than Mozilla many not give it a thought at all.

Re:How you can contribute to Firefox 57 success by yakult on Saturday September 02, 2017 @07:01PM (#15158706)
The telemetry probably shows that all the power users opted out of telemetry.
Re:How you can contribute to Firefox 57 success by krzyk on Sunday September 03, 2017 @03:26AM (#15160124)
It's the other way around I think, telemetry isn't (wasn't?) on by default and I enabled it on purpose. And I'm a power user, that's why I don't use chrome (1k tabs here).
Re:How you can contribute to Firefox 57 success by throwaway2048 on Saturday September 02, 2017 @04:18PM (#15157989)
Telemetry isnt the whole story, especially if it is being interpreted by somebody looking to justify decisions.
Re:How you can contribute to Firefox 57 success by Sir_Cmpwn on Saturday September 02, 2017 @07:38PM (#15158849)
I completely left Firefox over this and other bullshit.
Re:How you can contribute to Firefox 57 success by devcpp on Saturday September 02, 2017 @04:10PM (#15157945)
Sadly, I don't think the devs have much of a voice anymore. Corporate and upper management have taken over, as shown by the various SJW and usability debacles.

I'm always concerned of this happening to other large-scale independent FOSS projects. Special interests tend to take over without some benevolent dictator.

Re:How you can contribute to Firefox 57 success by kirillkh on Saturday September 02, 2017 @04:13PM (#15157962)
The devs still have a voice in the sense that they can always quit and fork. Or, in case of Firefox, join the Palemoon team.
Re:How you can contribute to Firefox 57 success by dblohm7 on Saturday September 02, 2017 @06:01PM (#15158454)
Joining Palemoon is highly unlikely - there's bad blood between the two communities.