Live data from Hacker News

Firefox Developer Edition

developer.mozilla.org

81–90 of 300 posts

Re: Firefox Developer Edition

#82
I'm taking advantage of the fact that there's a few Mozilla developers around to say a big thank you to the team.

I've never used most of the features of the developer edition except the console and everything is great on this developer edition.

I'm a proud owner of a Firefox OS phone and the simulator is really good and fast, I think I'm going to make an app or two during my spare time !

A big thank you to all the team for your great work !

Re: Firefox Developer Edition

#83
post #30

Getting a 50kB/s download rate for the Linux bzip. If anyone's going to find that annoying, it's developers!

Confirm, speeds are positively glacial here using the official Aurora updater. If nothing else, I suppose that indicates overwhelming popularity. :P

Re: Firefox Developer Edition

#84
post #15

That's great. Now if everyone else could have an up-to-date, experimental-feature-activated browser, this would be useful.

By everyone you mean other vendors? https://www.google.com/chrome/browser/canary.html http://devchannel.modern.ie/ http://www.opera.com/developer

I mean end users. I'd love to develop using one of these, but if 80% of the rest of the world can't see what I've done the way I see it when I do it, there's no real benefit here.

Re: Firefox Developer Edition

#86
post #74

Hi! Just a heads up that folks from the dev tools team will be monitoring this thread and are on-hand to answer questions. We'll try not to thread sit too much. :) In brief, the Developer Edition is a new release channel for Firefox, replacing Aurora (our pre-Beta channel). Everything else about the release cadence is the same. There are four major new features here: 1. The Firefox Tools Adapter ("Valence"), which le…

Wait, so this "Edition" will deliver the things that aren't even Beta? Is that only for development-only tools or also for features which will appear in "normal" Firefox? I think I'd prefer to develop for the current state of my user base and not for some "maybe it will be so" target. Can you please clarify what the "new rules" are?

It seems like they are referring to UI tools, not new HTML5 specs. Also, you can still debug with the other versions of FireFox.

Re: Firefox Developer Edition

#87
post #52

Will this version survive months of usage with multiple open tabs without performance deteriorating massively like the regular firefox? I left FF after my 10th profile reset / reinstall to get back to "normal" performance.

I swear this type of comment is becoming like a meme, it's pretty much repeated on every HN thread about Firefox. The response is standard too... Electrolysis. Wait for it. https://wiki.mozilla.org/Electrolysis/Roadmap

I don't see how e10s will fix any of the profile-based performance degradation issues that have existed in FF for years.

It will fix the crashing tab equals crashing browser issue, but that is a very different problem.

Re: Firefox Developer Edition

#89
post #66

Hi! Just a heads up that folks from the dev tools team will be monitoring this thread and are on-hand to answer questions. We'll try not to thread sit too much. :) In brief, the Developer Edition is a new release channel for Firefox, replacing Aurora (our pre-Beta channel). Everything else about the release cadence is the same. There are four major new features here: 1. The Firefox Tools Adapter ("Valence"), which le…

Built-in Postman-alike API builder.

This!

Re: Firefox Developer Edition

#90
post #74

Hi! Just a heads up that folks from the dev tools team will be monitoring this thread and are on-hand to answer questions. We'll try not to thread sit too much. :) In brief, the Developer Edition is a new release channel for Firefox, replacing Aurora (our pre-Beta channel). Everything else about the release cadence is the same. There are four major new features here: 1. The Firefox Tools Adapter ("Valence"), which le…

Wait, so this "Edition" will deliver the things that aren't even Beta? Is that only for development-only tools or also for features which will appear in "normal" Firefox? I think I'd prefer to develop for the current state of my user base and not for some "maybe it will be so" target. Can you please clarify what the "new rules" are?

The release process might help explain it: https://wiki.mozilla.org/RapidRelease or, if you're familiar with Chrome's stable / beta / dev / canary channels, it's largely the same model.

As far as fundamental web platform features are concerned, the Developer Edition is a normal pre-Beta channel. It's primarily that more willing to promote new tooling up from Nightly into the DevEdition or to set different default preferences, for instance.

Post reply on HN