Live data from Hacker News

Firefox Developer Edition

developer.mozilla.org

41–50 of 300 posts

Re: Firefox Developer Edition

#41
Exciting stuff! If you're already on Aurora, when you auto-update to developer edition, you'll switch over to the new dev profile and your bookmarks and settings will be gone. You can get at those by opening the profile manager and switching back to the default profile, or by using a stable version of Firefox.

https://support.mozilla.org/en-US/kb/profile-manager-create-...

Re: Firefox Developer Edition

#42
post #31

I noticed there's a checkbox for "make FirefoxDeveloperEdition my default browser," is that just a vestigial thing from the regular FF installer, or is it actually safe for me to use FFDE as my regular browser?

This page says "We'll include experimental tools that aren't yet ready to ride the trains to release." But https://hacks.mozilla.org/2014/11/mozilla-introduces-the-fir... says "It’s a stable developer browser which is not only a powerful authoring tool but also robust enough for everyday browsing." So maybe the browser part is stable, but the tools are experimental? And it uses a different profile by default, so a broken plugin can't step on your history, bookmarks etc.

Re: Firefox Developer Edition

#43
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 lets you use the Firefox dev tools to inspect and debug pages in Chrome for Android and Safari for iOS. The goal: one set of tools to debug any browser.

2. Side-by-side profiles. The Developer Edition defaults to a profile named `dev-edition-default`, which makes it easier to run Developer Edition at the same time as a normal release version of Firefox. You don't have to deal with the profile switcher each time.

3. Developer-friendly defaults. Developer Edition ships with things like remote debugging and browser-chrome debugging enabled by default.

4. And, for all of you who hated Australis, a compact theme with square tabs.

But those are just consequences of the single biggest change:

5. We have a new channel, which new rules. And we want to use it to build the best possible browser for web developers. We can ship new tools that aren't yet ready for the Beta channel, and we can change the browser's appearance and defaults specifically for web developers.

We'll be watching this thread during launch, but you can always submit feature requests on UserVoice. The right people will see them: https://ffdevtools.uservoice.com/forums/246087-firefox-devel...

This isn't a finished product. It's an invitation.

What tools do you need?

Re: Firefox Developer Edition

#44

Why emphatize on the download button that it is a "free download"? Maybe they'll add a payed option in the future?

I think you're probably reading too much into the 'free' bit - it says the same on the download for the normal Firefox. If anything, it's a play on it being "free as in freedom".

Re: Firefox Developer Edition

#46

WebIDE still feels like a toy for now. Very little customization for the text editor for now. Also the browser has a shiny new dark theme but the text editor doesn't seem to support themes (and has a light theme as default).

I have been using it for a few weeks, and I find it extremely useful. Not the editor itself (I'm currently test-driving Atom), but the ability to quickly send my app to all my devices and emulators, and remote debug it.

Re: Firefox Developer Edition

#47
post #9

Here's the prettier link to download: https://www.mozilla.org/en-US/firefox/developer/

I believe this is the stub (~400Ko) Sniffing my laptop gave me this http://download-installer.cdn.mozilla.net/pub/firefox/nightl... Felt weirdly generic since the name didn't indicate any special edition, but I ran it and it says developer edition. ---- tl;dr In case someone needs an offline installer, grab that url.

The subt stopped downloading in my crappy connection and gave me this link to the installer: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/late...

Edit: Use the custom installation option to prevent it from becoming your default browser.

Re: Firefox Developer Edition

#48

Why emphatize on the download button that it is a "free download"? Maybe they'll add a payed option in the future?

You get more clicks if you reassure people that it's free.

Edit: I'm serious, here's an example https://vwo.com/blog/ab-test-case-study-how-two-magical-word...

Re: Firefox Developer Edition

#49

Earlier quoted context omitted.

I believe this is the stub (~400Ko) Sniffing my laptop gave me this http://download-installer.cdn.mozilla.net/pub/firefox/nightl... Felt weirdly generic since the name didn't indicate any special edition, but I ran it and it says developer edition. ---- tl;dr In case someone needs an offline installer, grab that url.

The subt stopped downloading in my crappy connection and gave me this link to the installer: https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/late... Edit: Use the custom installation option to prevent it from becoming your default browser.

All that work for nothing, if only I had a crappy connection :)

Re: Firefox Developer Edition

#50

Just a rebranding of Aurora, focused on developers? I was expecting something more from all the fanfare.

There are new features (tools adapter, side-by-side profiles, compact theme, developer-friendly default preferences). But what's larger than any of that is the change in Mozilla's policy / conception of the pre-Beta channel. This is very much a v0 offering, of course, but it's an indication that we genuinely want to take developer feedback seriously and co-design this with you. We've given ourselves the freedom to sh…

Hm, so if I develop on this I will still have to test in the regular stable Firefox release, that seems unfortunate.

Having more tools in a developer edition compared to the regular version of the browser seems fine, but at least for me I would like run it with the same rendering engine my users are likely to run.

Post reply on HN