4 ms·

> dev tooling still leaves A LOT to be desired. Anything specific? Feel free to file bugs, we want to make it better :) https://bugzilla.mozilla.org/enter_bu

> dev tooling still leaves A LOT to be desired. Anything specific? Feel free to file bugs, we want to make it better :) https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&c...

thezilch 13y ago
Not bugs, but features. And frankly -- sorry to be short -- everything Chrome has (or doesn't yet). I and my colleagues use just about everything. I see a lot of these things landing in the FFs landing in the last week, so I can't commend those efforts enough. Literally, I don't want to have to ever install Firebug; it makes the browsing experience even more sluggish. And I would have probably never started using FF, a decade ago, if it wasn't for the tooling, and I would have never had a chance to convince as many friends and family to use FF. The same reasons I will just recommend Chrome, today. Frankly, you will have to have something that Chrome doesn't to bring us back, and it's been a long time coming for the tooling to be even on par. Again, I commend your efforts, because I think your community involvement and dev blogs are really great.
- idupree 13y ago
  My Chromium-using coworker is jealous of my (Firefox's) 3D View and my Responsive Design View. I use both browsers in order to have access to all the best tools. (I keep development separate from regular browsing, either through Incognito or separate Firefox profiles. This way, my regular browser addons don't distort my view of how-my-website-looks-to-most-people, and Firebug speed becomes irrelevant.)
  - thezilch 13y ago
    Your co-worker should know that both are available via an extension and native DevTools, respectively.
- mnemonik 13y ago
  We hear you and we are working on it. Just a note, we use bugzilla for everything, so if there is ever a specific feature you want, you can make a bug for that feature. For example, "integrate source maps with the debugger" was the title of a bug that I worked on.
nfm 13y ago
I'm loving the focus that's been going into the FF dev tools over the last few releases, they are improving rapidly and dramatically! One thing that irks me is inspecting returned JS values - I almost never want to see [object Array]. I vastly prefer the Chrome dev tools output: inline, expandable, and a meaningful representation for objects. Not a bug, but I think it would be a big improvement :)
- mnemonik 13y ago
  We're working on it :) BTW, we use bugzilla bugs for features too, so if you feel there is a specific feature missing, just open a bug for it.

thezilch 13y ago

Not bugs, but features. And frankly -- sorry to be short -- everything Chrome has (or doesn't yet). I and my colleagues use just about everything. I see a lot of these things landing in the FFs landing in the last week, so I can't commend those efforts enough. Literally, I don't want to have to ever install Firebug; it makes the browsing experience even more sluggish. And I would have probably never started using FF, a decade ago, if it wasn't for the tooling, and I would have never had a chance to convince as many friends and family to use FF. The same reasons I will just recommend Chrome, today. Frankly, you will have to have something that Chrome doesn't to bring us back, and it's been a long time coming for the tooling to be even on par. Again, I commend your efforts, because I think your community involvement and dev blogs are really great.

idupree 13y ago
My Chromium-using coworker is jealous of my (Firefox's) 3D View and my Responsive Design View. I use both browsers in order to have access to all the best tools. (I keep development separate from regular browsing, either through Incognito or separate Firefox profiles. This way, my regular browser addons don't distort my view of how-my-website-looks-to-most-people, and Firebug speed becomes irrelevant.)
- thezilch 13y ago
  Your co-worker should know that both are available via an extension and native DevTools, respectively.
mnemonik 13y ago
We hear you and we are working on it. Just a note, we use bugzilla for everything, so if there is ever a specific feature you want, you can make a bug for that feature. For example, "integrate source maps with the debugger" was the title of a bug that I worked on.

nfm 13y ago

I'm loving the focus that's been going into the FF dev tools over the last few releases, they are improving rapidly and dramatically! One thing that irks me is inspecting returned JS values - I almost never want to see [object Array]. I vastly prefer the Chrome dev tools output: inline, expandable, and a meaningful representation for objects. Not a bug, but I think it would be a big improvement :)

mnemonik 13y ago
We're working on it :) BTW, we use bugzilla bugs for features too, so if you feel there is a specific feature missing, just open a bug for it.