Ask HN: Webdevs, designers: what devtools should we (Mozilla) build in Firefox?

Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by paulrouget on Tuesday March 05, 2013 @12:37PM (#5325947)

Our team also work on Firebug. So no, it's not "discontinued".

We are working on sharing more code. In an ideal world, we will be able to merge these 2 tools in the future.

[ Parent | on HN ]

Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by gcp on Tuesday March 05, 2013 @12:46PM (#5326024)

But does "work on" mean "maintain so it doesn't break" or "actively improve"?

[ Parent | on HN ]

Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by campd on Tuesday March 05, 2013 @02:49PM (#5326873)

Jan Odvarko, the current maintainer of Firebug, is on our team. He's currently the only Mozilla employee dedicated to the Firebug project. He's joined by a healthy community (you can follow the project at https://github.com/firebug/firebug).

Jan and the Firebug team are actively improving Firebug - not just maintaining it so it doesn't break. The bulk of the Mozilla staff (and our volunteer community) is focused on the built-in tools, but a lot of it ultimately benefits the Firebug team.

The standby example is our debugger. A lot of the performance and stability problems Firebug has are a symptom of the old Spidermonkey debugging API (JSD). The developer tools and Spidermonkey team built a new debugging API[1] along with a remote debugging server. The Firebug team is currently working to update Firebug to the new debugging API/remote server.

Most of our work is dedicated to the built-in developer tools. But those also support Firebug development.

[1] https://wiki.mozilla.org/Debugger

[ Parent | on HN ]

Re:Ask HN: Webdevs, designers: what devtools should we (Mozi... by schrijver on Wednesday March 06, 2013 @03:59AM (#5330194)

Merging these two tools would be by number 1 request.

[ Parent | on HN ]