Live data from Hacker News

Firefox 70 released for Firefox Quantum: Developer Edition

mozilla.org

81–90 of 116 posts

Re: Firefox 70 released for Firefox Quantum: Developer Edition

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

Ooh, that's a very nice change. I've stubbornly stuck to Safari on my laptop because of its low power usage.

Now I'd be losing the tabs/bookmarks integration with iOS's unchangeable default browser, but that's not as big a deal to me.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#82
post #78
post #74

Earlier quoted context omitted.

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?

Maybe. This was but one improvement in a backlog.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#83
post #70

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.

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

Great news. This is the only thing I open chrome for! Thanks for the info.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#84

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.

The title rule encourages blogspam and bad articles. For example if Google were to make a big change their ToS and you link to it, the title would be "Google ToS". This is confusing. So in instead you link to some crappy article with a better title about the same subject. Or not at all.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#85
post #71

Earlier quoted context omitted.

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.

The selection of the article itself is sufficient to add spin.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#86
post #71

Earlier quoted context omitted.

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.

The selection of the article itself is sufficient to add spin.

I don't think I understand.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

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

The Chrome profiler is a lot better (IMO) than the one Firefox ships. But then there is https://profiler.firefox.com/

The debugger/sources view in Firefox also seems buggier still. E.g. a lot of times while it correctly displays source-mapped locations in the console, clicking on those source links will not actually go to the right place in the source view (it will either end up in the packed source or it will not go to the correct line in the source-mapped file even tho the console link gave the correct line).

One thing I miss that Firefox does not have at all is the Layers view. Which would be especially important since such things are browser specific and debugging performance/memory issues and making sure the engine uses a sane set of compositing layers can be important sometimes.

But the feature I miss most in my tiny corner of the world by a large margin is the Websocket support indeed. This is the thing that always makes me go back to Chrome devtools.

Re: Firefox 70 released for Firefox Quantum: Developer Edition

#90

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…

Did you ever post your proposal to the mozilla dev mailing as requested by jdm?

I'd like to read the discussion but can't find anything in the archives.

Post reply on HN