Live data from Hacker News

Firefox 57.0 Released

mozilla.org

731–740 of 836 posts

Re: Firefox 57.0 Released

#731

Earlier quoted context omitted.

There certainly is hardware acceleration in Firefox on Linux, more then likely it has been disabaled because of your configueration/set-up/drivers. To turn it on go into your "about:config" and toggle the entry "layers.acceleration.force-enabled" to "True" and restart. Then Firefox is as fast as Chrome or faster, simple as that. Although it would be nice if there was a dialog telling the user their setup is incorrect…

>There certainly is hardware acceleration in Firefox on Linux, more then likely it has been disabaled because of your configueration/set-up/drivers. To turn it on go into your "about:config" and toggle the entry "layers.acceleration.force-enabled" to "True" and restart. Implying that it wasn't deliberately disabled. HW acceleration on Linux isn't enabled by default, and for good reason. Until those underlying reasons…

Are there any articles that elaborate on what work still needs to be done?

Re: Firefox 57.0 Released

#732

Earlier quoted context omitted.

Have you seen the Firefox backlog? If they'd gone for 100% API parity before the switch, we'd have had to wait another three years for e10s, and I don't know if that would have been survivable. I'm not happy about the situation as it stands, and I don't expect anyone else to be. I would be a lot more not happy about having to switch to Chrome because Firefox had become unusably slow - which it had already more or les…

> I have a hard time seeing how any of that would be preferable. Not to you. But not everyone cares about the same things. I have used Firefox as my main browser ever since it split off from Mozilla Suite. Personally, I have never, in the whole history of Firefox had a problem with its speed. At various points I might have had some problems with stability, some problems with compatibility and some problems with memor…

> A warning of some sort would be nice before breaking so much functionality

There have been periodic warnings on HN's front page for two years.

Re: Firefox 57.0 Released

#733
post #698

Earlier quoted context omitted.

This isn't quite true. Support for legacy extensions is disabled by default, but can be re-enabled via the `extensions.legacy.enabled` flag in about:config.

Though you lose multi-process operation, I think....

only on incompatible MP plugins.

however I've just ran nightly and although it says vimfx will work as a legacy plugin it's not working, so the deal's off. I shall not use my mouse!

Re: Firefox 57.0 Released

#735
post #692

Earlier quoted context omitted.

My browser and extensions did useful things yesterday that they do not do today. Who changed something in the meantime? Obviously I paid nothing for Firefox and Mozilla owes me the same nothing in return, but if it wants to keep users and remain significant, breaking arguably its main advantage might not be the best plan.

> ... but if it wants to keep users and remain significant, breaking arguably its main advantage might not be the best plan. I fully expect that this move will certainly lose Mozilla a few Firefox users, but on balance it'll be a net win: they were already losing users to performance problems and lack of modern security features. The users the lose due to lost extensions will be tiny compared to the users they won't…

> I fully expect that this move will certainly lose Mozilla a few Firefox users, but on balance it'll be a net win

I certainly hope so, for the sake of an open web. Hope they can take on the universal pushing and bundling that Google does with Chrome. Anecdotally I can say that none of my acquaintances are even aware of Firefox because Chrome can with their OS and they never saw a need to look beyond it. I hope Mozilla has a clear strategy to advocate and market Firefox, since technical merit alone is not going to out-compete Chrome's entrenched position.

Re: Firefox 57.0 Released

#736
I've been using Firefox nightly after Quantum changes got in and I love it. I use it as my default browser.

Now that the changes are mainstream I'll be switching to version 57.

But I can't stop using Chrome yet. We write a lot of functional tests and Chrome is better at it.

It's got libraries like Puppeteer, good Webdriver support and a headless mode that just works. I can't put my finger on it, but it's difficult to run automated tests with Firefox.

I hope Firefox gets something like Chrome's DevTools protocol.

Re: Firefox 57.0 Released

#738

Earlier quoted context omitted.

Simply false. You don't appear to know what you're talking about, so maybe you should stop pretending. https://bugzilla.mozilla.org/show_bug.cgi?id=1215061

Anyone can read the bug report there and see what actually happened. Nobody even tried to detail what they needed until the VimFX came around a year ago to do so, and to begin workin on an experimental API. That experiment didn't really bear fruit until TWO MONTHS AGO, when the Firefox devs were knee-deep in the release cycle of their biggest product launch since version 1.0. So yeah, the Firefox devs didn't have muc…

That's not really the full picture.

One of the lead Firefox extension API devs is also the primary Pentadactyl (and former Vimperator) dev. I'm sure they were aware of exactly what was needed for that and similar extensions. They also made it clear from their earliest announcements that they intended supporting these extensions.

It simply isn't a priority which may be fair enough.

Pentadactyl still works well on ESR.

Re: Firefox 57.0 Released

#740

Earlier quoted context omitted.

TMP beta is a web extension.

Can you post a link? I have looked at their site and all current builds, including dev say that they are not 57 compatible.

Sorry, I may have heard wrong. I personally just stopped using the addon.
Post reply on HN