Live data from Hacker News

Firefox 70 released for Firefox Quantum: Developer Edition

mozilla.org

31–40 of 116 posts

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#33

Did they fix the memory bloat on Mac OS? It’s pretty much useless to me on MacOS.

Wondering about this as well.

On my 2017 MacBook Pro with touchbar I don't notice the performance hit, but on my 2015 MacBook Pro the whole system freezes with Firefox. What completely solves this however is enabling 'low res mode' (right click app icon -> get info -> check the low-resolution checkbox). But, as the name suggest, Firefox now runs in non-retina resolution. It looks crappier, but I still prefer it to other browsers.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#34

Did they fix the memory bloat on Mac OS? It’s pretty much useless to me on MacOS.

I saw a tweet recently about macOS power consumption fixes: https://mobile.twitter.com/pcwalton/status/11661937700160798...

Haven't noticed any memory bloat myself though (= it consumes a lot of memory, like any browsers). It's somewhere between Safari and Chrome.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#35
post #3

I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.

I miss ctrl-g as go to line. Is it possible to remap Firefox keyboard commands?

To my knowledge, no. They said they were working on it ages ago when they introduced the commands API for webextensions, but I don't think it is high on their priority queue.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#36
post #29
post #3

I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.

I tried FF dev edition with Angular, it was getting randomly slow. Weird issues popping while debuging typescript code. In the end I have to use Chrome for my work, even though I would like to drop Chrome personaly. That said, I sometimes have to debug Angular applications on IE11 which is worst nightmare...

I had similar experiences with a Vuejs application where I rendered thousands of "reactive" elements. The Chromium JS engine had substantially better performance then the Firefox JS engine.

However, to be fair, this is a strong sign that as a developer, we are doing something wrong. If a JS application feels slow on an average browser in an average computer, it will feel slow on all slower computers. The usability will be crap. In this particular example, the frameworks are not suitable for such a large number of "reactive" elements.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#37

Earlier quoted context omitted.

If you just want to be able to install unsigned extensions with neither the extra bugs from running a beta nor the telemetry, you can use the far less advertised "unbranded builds" of Firefox [1] instead. [1]: https://wiki.mozilla.org/Add-ons/Extension_Signing#Latest_Bu...

Don't the unbranded builds also lack automatic updating?

It's possible. Last I heard was that the unbranded builds were too eager to update [1] so it could well have been disabled totally. The Mozilla wiki doesn't mention anything about updating being disabled which to me implies it is not. If you find out for certain, please let me know!

I don't personally use the builds as Mozilla has not yet blocked signing of our extensions and `web-ext run` serves me well for development. Automated signing is not brilliantly documented but works well enough [2-3] to ensure that our builds are tested by real users before we release a stable version.

[1]: https://www.ghacks.net/?p=123637

[2]: https://github.com/tridactyl/tridactyl/blob/f45c990eac074df8...

[3]: https://github.com/tridactyl/buildbot/blob/master/autobuild....

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#38
post #18

Earlier quoted context omitted.

Each has their pros and cons. My favorite features in FF devtools which are missing from Chrome are CSS diff and the advanced filtering in the network panel. Chrome filtering only works on hosts, while FF can filter in query strings and other sections of a request.

I often use network filtering in Chrome devtools to find requests by query string. If you start typing into the search box it matches it against the whole request including url parameters.

You're right, that works. Either that landed recently, or I'm confusing with another filtering feature that Chrome is missing.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#39
post #29
post #3

I can't seem to make the switch away from Chromium devtools. I don't know whether it's because I am habituated to the Chromium ones or whether there is something klunky about the Firefox devtools that I can't put my finger on.

I tried FF dev edition with Angular, it was getting randomly slow. Weird issues popping while debuging typescript code. In the end I have to use Chrome for my work, even though I would like to drop Chrome personaly. That said, I sometimes have to debug Angular applications on IE11 which is worst nightmare...

I use Firefox developer edition as my main browser, and there does seem to be some issue with Angular sites. admin.google.com is particularly bad – but so bad it makes me wonder if they only test in Chrome.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#40
post #4

Earlier quoted context omitted.

They are not, apparently the reasoning was not to make Firefox bigger with needless features not requires by non-techie users. At least this is how I recall it, please anyone correct me if I am mistaken.

It's a beta with special features for developers. right now dev edition for me is 70.0b1 regular is firefox 68.0.2 It also has the new logo and I suppose there's new stuff on the dev tools. "What's new" page is broken so not absolutely sure.

Definitely a few developer friendly plugins like one that parses and renders JSON responses in a new tab instead of showing unformatted plain-text.
Post reply on HN