Live data from Hacker News

Firefox 70 released for Firefox Quantum: Developer Edition

mozilla.org

51–60 of 116 posts

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#51
post #44
post #6

Earlier quoted context omitted.

Special features: kind of like an IDE on top of Firefox, meant to be used by web developers. Comes with its own config profile, so you can fuck around and not break stuff in stable/beta that you are supposed to have concurrently installed. Kind of like beta: all of the new APIs and features related to web development are there three months before they hit stable.

The retail edition of Firefox already includes dev tools.

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

Re: Firefox 70 released for Firefox Quantum: Developer Edition

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

In Chromium in the Network tab how do you see the request? In Firefox you can edit and resend a request and see it or modify it and send it again.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#54

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?

It is based on the beta release channel and has some configuration tweaks. See https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Dev...

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#55

What’s the Mozilla community like for external contributions? Before the big google dollars it seemed cliquey and now seems mostly paid people. Is that accurate ? I wonder what happens to Firefox if the search dollars run out and companies are uniting behind chrome/WebKit

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), some enterprises, and many contributors (I wonder if chromium has more opensource non paid contributor than gecko)

Servo is mostly developed by paid mozilla devs, but had major improvements made by contributors. Proportionally far more non paid contributor than the gecko of today, I expect mostly because they work on github which is more friendly than bugzilla and mailing lists...

Gecko dev today non paid developers are a few minority.

If Firefox does not die by himself, expect Google to slowly stop paying them Thus mozilla will die which would be a great loss.

Mozilla could save it's future, mozilla could become sustainable: I made a proposal here: https://github.com/servo/servo/issues/24026

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#56
post #28

Earlier quoted context omitted.

Having recently switched to Edge Dev after having used Firefox for roughly a year (and Chrome before that), I'd say Firefox devtools' strongest point are the style editing stuff. Somehow Firefox devtools feel a bit clunkier when working on JS projects but they offer a lot of neat gimmicks if you dig into the depths of CSS. I also find the guidelines when highlighting an element more helpful than in Chromium for align…

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.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#57
post #30

Would love to see something like this for Android (Android firefox doesn't have developer tools to save space).

It's not to save space, they could download it opt-in.. It's because they don't have the resources and have many P1 features to catch up.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#58

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.

Random question: Do you use safari? Do you see significant performance differences with chrome? Do you see broken/partially broken websites on safari vs chrome ?

Re: Firefox 70 released for Firefox Quantum: Developer Edition

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

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#60

What’s the Mozilla community like for external contributions? Before the big google dollars it seemed cliquey and now seems mostly paid people. Is that accurate ? I wonder what happens to Firefox if the search dollars run out and companies are uniting behind chrome/WebKit

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 :(
Post reply on HN