Live data from Hacker News

Firefox 58

mozilla.org

91–100 of 197 posts

Re: Firefox 58

#91
post #53
post #46

Earlier quoted context omitted.

IIUC the API needed for this addon[1] will be available in FF 59[2]. Mozilla dropped support for Tab Center a while before Quantum IIRC. Another addon took its place, but then was dropped by its developer with Quantum. Supposedly [1] will allow transition from the older addons. I'm looking forward to finding out once 59 is out. [1] https://addons.mozilla.org/en-US/firefox/addon/tab-groups/ [2] https://bugzilla.mozill…

That bugzilla link is purple, so I guess that's the right one. But there's just so many APIs that were missing when they forced 57 on everyone, I honestly don't actively keep track because it's going to take a while. They were nowhere near ready, but a fixed release schedule is a fixed release schedule... Edit: Looking at the status: > Status: NEW → RESOLVED 4 days ago That could have made it into 58. Or they can sti…

The feature landed in the nightly trunk, it has to go through the alpha/beta release channels.

Re: Firefox 58

#92
post #81

Earlier quoted context omitted.

Google inbox is terrible on ff, this is vendor lock-in by google, the new MS

Not really, it works fine on Safari.

Which shared a lot of roots with Chrome. It's probably that they are optimizing for things that are fast in Chrome's JavaScript engine, which isn't necessarily what's fast in Firefox's Javascript engine.

Re: Firefox 58

#93
Firefox has improved dramatically since 57 and I'm using it more now, but the one reason why it's still not my main browser is that new windows open too slowly.

The extra lag can't be much more than 100 ms or so (if that), but opening new windows is the worst possible moment to be a little bit slower than other browsers (on macOS).

Re: Firefox 58

#94
post #85

Earlier quoted context omitted.

Yeah, the browser has gotten snappier. But then I pop open the dev tools and they're unbearably slow - like I simply can't do real dev work in FF anymore, have to use Chrome. It may be that I tend to do a lot of development with Web Components, which FF still doesn't have natively (though Custom Elements are live in 59/nightly, right?!), but either way it seems like a failing of the tooling that it beachballs for 5-1…

This is strange. FF dev tools are a lot quicker for our apps then the Chrome dev tools. In fact, the Chrome dev tools are snail speed compared to the FF ones. Again, this might be related to the type of app you are developing.

Try this: From the "Inspector" tab, click on any CSS file in order to open the Style Editor. Loading the file and then scrolling to the relevant part is much slower than Chrome if you do this on a page with several stylesheets.

Re: Firefox 58

#95
post #2

Simply linking to the download page isn't particularly useful, IMO. Release notes are here: https://www.mozilla.org/en-US/firefox/58.0/releasenotes/

And since this is HN, the download people here are most likely to want is the Developer Edition: https://www.mozilla.org/en-US/firefox/developer/

You can't disable telemetry in the Developer Edition for some reason, so I've gone back to Stable.

Re: Firefox 58

#96
post #42
post #24

Earlier quoted context omitted.

Yeah, it positively was , and it would lock the browser up with misbehaving tabs. I managed to use Fx50 (or so, I forget the exact release) for about a day before going "nope, back to Chrome, it might chew batteries like crazy but at least it's fast." Firefox has significantly improved and deserves praise for it. Rewriting history to always be at war with Eastchromea is unnecessary.

This seems to be a weird thing: I've been om FF the while time and I'm impatient. In the other hand I've no reason not to believe it when so many people report performance issues. My best guess is a combination of different browsing habits and/or different hardware/os. (My browsing habits are mostly hn, local news and pages I work on and I've had decent hardware running various versions of Linux and Windows.)

I've found some stuff to be a bit slower on new FF since I made the switch when Quantum came out, but I chalk that up to heavy use of some Google webapps in which the chrome optimizations might have the opposite effect on a different JavaScript engine, and heavy use of containers, which are awesome.[1]

1: At first I didn't know how to get sites to default to a container, so kept having to close and reopen tabs to get the right contianer, but once I figured that out, it's smooth.

Re: Firefox 58

#97
post #18

Did canvas fingerprinting blocking make it to this release? There were many articles saying it might or will happen and I can't find anything backing this up in the release notes. https://duckduckgo.com/?q=firefox+58+canvas+fingerprinting&t...

According to https://bugzilla.mozilla.org/show_bug.cgi?id=967895 it's in 58 but wasn't added to release notes because it's disabled by default via the privacy.resistFingerprinting about:config setting.

It also breaks the built-in screenshots: https://bugzilla.mozilla.org/show_bug.cgi?id=1412961

Re: Firefox 58

#98

I've gotten into a habit of checking into all the performance boosts on Firefox release, but I almost missed the best feature of the release: Tracking Protection! It's buried under Preferences -> Privacy & Security -> Tracking Protection I've been using Privacy Badger for a while and today installed DDG's new Privacy Essentials. Does anyone know how the new Firefox feature compares to these other 2 options regarding…

This was actually released already in Firefox 57 as mentioned in the "in case you missed it" section at the bottom of the new features list.

Re: Firefox 58

#99
post #8

I wrote up a more detailed look at some of what's in Firefox 58: https://hacks.mozilla.org/2018/01/firefox-58-the-quantum-era...

How does one end up in a position to do this work at Mozilla? I'm currently looking for a new SWE role, would absolutely love to work on Firefox.

Current openings are posted at https://careers.mozilla.org/. There should be a steady trickle of opportunities as 2018 budgeting wraps up and requests for headcount get approved over the coming weeks and months.

We do most of our work in the open, so there's a wealth of information you can gather before applying for a role or interviewing. Lurking on mailing lists, reading Bugzilla, following GitHub repos, etc. are all great ways to become familiar with how Mozilla works, the challenges we face, and where you'd best be able to have an impact.

Re: Firefox 58

#100

Since release 57 I have almost exclusively started using Firefox on Android. I know most quantum enhancements aren't yet in the Android version but something improved leaps and bounds at 57. The ability to use sync and various privacy enhancing extensions mean FF has a great appeal on Android. Now only if they can fix the remaining URL load delays and improve video playback compatibility it'll be a great experience.

I think and early version of the enhancements on Android are available in 58, and can be enabled by using the search bar to enter `layout.css.servo.enabled` and then switching it on.
Post reply on HN