Live data from Hacker News

Firefox 70 released for Firefox Quantum: Developer Edition

mozilla.org

71–80 of 116 posts

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#71

Earlier quoted context omitted.

I really wish posts like this, and posts that are just random Wikipedia articles, would have a paragraph (or at least a sentence) from the submitter. Why is this interesting? For Wikipedia articles about people this is doubly important because the title is inevitably just the person's name - unless you already know who that person is there's no hint as to why they are significant.

Disagree. I like the way this system stops submitters giving their potentially half-baked opinions on articles, and adds an element of mystery to things.

I'm inclined to agree, tossing in the poster's spin tends to drive the topic, often to odd places rather than the actual thing.

At the same time links to pages without any context as to why leaves me wondering why I should be looking at this page. Particularly product pages that are not easy to parse what the point is sometimes.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#72
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.

Does anyone know why Chromium hasn't fixed this supposedly old regression bug where opening large minified js file in the source tab hangs the whole tab/browser, sometimes for more than 10 seconds even on a fast machine. Can't this be done asynchronously or at least give the user a way to cancel loading it? If you open a large file and then close developer tools, reload the page and open developer tools again, it will try to reopen the last opened file again, blocking chrome for another 10 seconds. Very annoying.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#73

Earlier quoted context omitted.

I regularly watch commits from webkit, chromium, gecko-dev and servo. Webkit is developed almost exclusively by Apple (or more maintained because development is very slow, btw I suspect that Apple will drop webkit as it become too far behind) There are also a few igalia devs and one Sony dev + one Gmail dev. Chromium is developed by so many people, Google, Microsoft, opera, QT, hardware makers (ARM, Intel, nvidia), s…

What a terrible argument. I really don’t understand how people don’t see the negative effects of browser monoculture. I feel like I’d just be rehashing the same old points :(

Which argument? Firefox is dying, it's a fact, watch the marketshare over time.

Were you referring to my proposal on github?

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#74
post #65

Earlier quoted context omitted.

The Quantum version of Firefox (and Firefox Developer) did not come out this morning. You likely just got a routine build update.

It bumped up from 69 to 70 this morning, a "major" update so much as browsers have those anymore. But it's not clear what's actually new in this. Here's what they listed for 70.0a1 back in July, but the release notes link for today's update is a dead end. https://www.mozilla.org/en-US/firefox/70.0a1/releasenotes/

Dev edtition gets the last nightly build two weeks before the same release hits Beta channel.

One of the main changes for me as a Mac user is this: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#75

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

Just a few days ago one of the first fixes got into the code (v70 already has this): https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32

It's night and day on some pages, like google docs word document, for example.

PS: this one is about power\cpu usage though. Never really had any memory problems on my macs.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#76

Earlier quoted context omitted.

While I mostly agree, I do switch to Chrome every once in a while when the javascript stacktrace in FFdev is a bit unclear. Chrome usually seems to be a bit better. But I always switch right back to FF.

Debugging fancy JS frameworks in firefox (for me, unexperienced js user) is more painful than in chrome, but debugging js in webbrowser is pain anyway

In Angular (which I like) I have found that there is a bug in error logging that only occurs on Firefox.

So every time I stumble upon that I'll open Chromium, find the stack trace and go back.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#77
post #29

Earlier quoted context omitted.

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.

Error logging used to be broken in Firefox at least until last year. I'm not working in frontend at moment and I never got around to submitting a bug (it always happened while at work) but my opinion was that there was a bug somewhere in there where they used a Chromium only API.

And yes, I too have wondered if they only test in Chrome.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#78
post #74

Earlier quoted context omitted.

It bumped up from 69 to 70 this morning, a "major" update so much as browsers have those anymore. But it's not clear what's actually new in this. Here's what they listed for 70.0a1 back in July, but the release notes link for today's update is a dead end. https://www.mozilla.org/en-US/firefox/70.0a1/releasenotes/

Dev edtition gets the last nightly build two weeks before the same release hits Beta channel. One of the main changes for me as a Mac user is this: https://bugzilla.mozilla.org/show_bug.cgi?id=1429522#c32

Does this mean Firefox won't always be the "apps using significant energy" list?

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#79
post #56

Earlier quoted context omitted.

What percentage of your users are on IE11? Did you measure if there's at least one user on IE11?

Nearly 100%. Welcome to German enterprise intranets. The only good thing is that when the new Edge enters general availability, we can likely get rid of 100% of our IE11 users for good.

Having to fight with IE11.. You are one of the heroes of modern times ^^

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#80
post #44

Earlier quoted context omitted.

The retail edition of Firefox already includes dev tools.

...and Firefox Developer comes with dev tool features that have not yet reached Firefox Stable.

Which ones are not in the stable version yet?
Post reply on HN