14 ms·
Developer Edition is a pre-beta version of Firefox (the core code goes from Nightly -> DevEdition -> Beta -> Release, much like Chrome goes from Canary -> Dev -
by callahad 11y ago
Developer Edition is a pre-beta version of Firefox (the core code goes from Nightly -> DevEdition -> Beta -> Release, much like Chrome goes from Canary -> Dev -> Beta -> Stable). DevEdition also ships with some more minor customizations to ease development: a separate default profile, buttons in the toolbar for the Developer Tools, etc.
The plateau you're referring to is probably due to the team's focus this quarter on building the all new performance tool, making sure all the tools work with process separation (e10s), and trying to squash bugs around polish and stability. The next few quarters will likely see a return to pushing on user-visible features.
We also have an opening for a full-time interaction designer on the DevTools team. If you dig this stuff, or know someone who does, please consider applying at https://careers.mozilla.org/en-US/position/oLiW0fwJ https://careers.mozilla.org/en-US/position/oLiW0fwJ
- CWuestefeld 11y agoIs it possible to have side-by-side installs of the current stable release as well as developer edition?
- phs2501 11y agoDo you have a timeline for getting proper (source-mapped) file/line numbers in the console (and performance tools, I just checked and it's absent from there as well)? This is currently the main reason I reach for Chrome when I need to write JavaScript. I see this bug marked devedition-40: https://bugzilla.mozilla.org/show_bug.cgi?id=670002 https://bugzilla.mozilla.org/show_bug.cgi?id=670002 but I still see "bundle.js:23796" in my console in Dev Edition 40, which is less than useful.
- jsantell 11y ago[member on the devtools team] A strategy and implementation for source maps across all tools is something we're actively working on. It's frustrating for us as well when working on side projects, if that is any indication of how much we'd like to get source maps everywhere