Live data from Hacker News

Firefox 70 released for Firefox Quantum: Developer Edition

mozilla.org

61–70 of 116 posts

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#61

Earlier quoted context omitted.

This is why I dislike these software posts without context. It's never clear if there's been an update or if the submitter just discovered them for the first time.

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.

[deleted]

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#62
post #5

Can anyone explain exactly what's different about this? Are all these features not in normal Firefox? Is this like a beta of normal firefox, set of extensions, or a significant fork?

I think it's mainly a difference in configuration. The developer version, IIRC, allows you to install extensions on your own machine without seeking approval from Mozilla, but on the other hand it apparently subjects you to additional telemetry: > Firefox Developer Edition automatically sends feedback to Mozilla ... In addition to the data collection described in this Privacy Notice, these versions by default may sen…

> allows you to install extensions on your own machine without seeking approval from Mozilla

Unless it changed quite recently, you can do this with normal Firefox builds too AFAIK

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#63

Earlier quoted context omitted.

Other than the web socket support in Chrome, the FF dev tools are a billion times better than Chrome now. I cannot work without the css layout overlays from FF dev tools. Makes working with grid layouts insanely easy.

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

Re: Firefox 70 released for Firefox Quantum: Developer Edition

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

As others have pointed out, it may be worth looking into whether or not your reasons for using Chromium for the devtools are simply habit.

Speaking for myself, I'm in the other camp. I never really ditched Firefox for Chrome except for a brief period[0]. I returned to Firefox back when it was still called "Firefox (Not Responding)". Other than the renaming (/s), it -- generally -- flies. The devtools do what I need them to do, however, I used to hop back and forth from Chromium to FF a lot more.

So I'll be re-evaluating things, again, myself -- just in the other direction. :)

[0] I used Chrome for about two years after its release because Firefox wouldn't work with an internal application. It was just easier to use a single browser.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#65
post #59

Should the title have a (2017) at the end, since Quantum initially came out then[0,1]? (I understand it points to a current-version but it seems like, from the comments, it's being mistaken for having recently been released.) [0] - https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-bet... [1] - https://en.wikipedia.org/wiki/Firefox_version_history#Firefo...

No, i'm using the developer edition and got the update only this morning. But I don't know if something have changed...

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

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#66
post #59

Should the title have a (2017) at the end, since Quantum initially came out then[0,1]? (I understand it points to a current-version but it seems like, from the comments, it's being mistaken for having recently been released.) [0] - https://blog.mozilla.org/blog/2017/09/26/firefox-quantum-bet... [1] - https://en.wikipedia.org/wiki/Firefox_version_history#Firefo...

No, i'm using the developer edition and got the update only this morning. But I don't know if something have changed...

Today updated to 70.b1, according to the About Firefox Developer Edition window.

It has a "What's new" link next to the version number, but it links to a 404: https://www.mozilla.org/en-US/firefox/70.0beta/releasenotes

EDIT - I put in a bug report on the release notes link, response says that release notes will come out next week

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#67
post #62
post #5

Earlier quoted context omitted.

I think it's mainly a difference in configuration. The developer version, IIRC, allows you to install extensions on your own machine without seeking approval from Mozilla, but on the other hand it apparently subjects you to additional telemetry: > Firefox Developer Edition automatically sends feedback to Mozilla ... In addition to the data collection described in this Privacy Notice, these versions by default may sen…

> allows you to install extensions on your own machine without seeking approval from Mozilla Unless it changed quite recently, you can do this with normal Firefox builds too AFAIK

It changed, but not really that recently.

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/Web...

Note specifically the step where the addon must be signed before it can be installed in this fashion. "Developer edition" does not require you have Mozilla's permission to install addons.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#68
post #65
post #59

Earlier quoted context omitted.

No, i'm using the developer edition and got the update only this morning. But I don't know if something have changed...

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/

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#69

Earlier quoted context omitted.

This is why I dislike these software posts without context. It's never clear if there's been an update or if the submitter just discovered them for the first time.

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.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

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

Other than the web socket support in Chrome, the FF dev tools are a billion times better than Chrome now. I cannot work without the css layout overlays from FF dev tools. Makes working with grid layouts insanely easy.

I think they're almost done with the first iteration of WebSocket support in the Firefox DevTools. Might even already be in Developer Edition: https://bugzilla.mozilla.org/show_bug.cgi?id=885508
Post reply on HN