But does it not slow everything down horrendously?
No, that's the old firebug. There was a platform bug in Firefox linked to the usage of the old javascript debugger module. This version of Firebug is completely unaffected.
Firebug 2.0
11–20 of 123 posts
Re: Firebug 2.0
#12Earlier quoted context omitted.
Can you explain why? I've never found a use case that it covers better than Chrome, and it seems to bloat FF a bit. But I'm very willing to believe I just don't understand what it offers.
Chrome still does not support multiline JS console (you need to shift-enter every single lines) See: https://code.google.com/p/chromium/issues/detail?id=35487
That is useful, but doesn't really seem to cover the original comment's assertion that Firebug is still "inarguably the best"
Re: Firebug 2.0
#13Re: Firebug 2.0
#14I used to use Firebug extensively. These days, the built-in Firefox developer tools seem to cover everything I need.
I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.
Re: Firebug 2.0
#15I really need to stop being so dependent on Firebug. I've done coding sessions or interviews where the other developer only has Google Chrome. Since I use Firebug so much, I am not as proficient with Chrome Dev tools. It makes me look like an amateur when I fumble around. Half the time saying I am used to Firebug is useless since they don't even know what it is.
Re: Firebug 2.0
#16I use Chrome or Firefox built in developer tools, however I still think Firebug fits my workflow the best. Unfortunately it's too slow to use.
The thing I miss the most is the inline display of AJAX call responses, and being able to write/run multi-line snippets of JavaScript (without ctrl+enter).
Somewhat interestingly, Firefox built their entire add-on architecture because Joe Hewitt wanted dev tools (for debugging the actual browser moreso than websites), and Firebug was split off from Firefox and made into an add-on. A decade later, this has reversed and every major browser now ships with integrated dev tools.
Re: Firebug 2.0
#17I use Chrome or Firefox built in developer tools, however I still think Firebug fits my workflow the best. Unfortunately it's too slow to use. The thing I miss the most is the inline display of AJAX call responses, and being able to write/run multi-line snippets of JavaScript (without ctrl+enter). Somewhat interestingly, Firefox built their entire add-on architecture because Joe Hewitt wanted dev tools (for debugging…
"too slow to use" -- it now uses JSD2, which is much faster. So you may want to give a try again, as your previous experience may no longer be valid on this point.
Re: Firebug 2.0
#18Video walk through of what is new: https://www.youtube.com/watch?v=LtgLX5vZZSI
Re: Firebug 2.0
#19I really need to stop being so dependent on Firebug. I've done coding sessions or interviews where the other developer only has Google Chrome. Since I use Firebug so much, I am not as proficient with Chrome Dev tools. It makes me look like an amateur when I fumble around. Half the time saying I am used to Firebug is useless since they don't even know what it is.
So what if you are the black sheep of the shed?
Re: Firebug 2.0
#20Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.
I'm always surprised when I read comments about how the Firefox devtools offer the best developer experience. Every single one of these new features (except searching the dom via CSS selectors or regex) have been available in Safari's Web Inspector for OS X for at least a year. Plus, I think the UI is more thought out and easy to use in Safari. Can someone explain what Safari's Web Inspector is lacking?
publicity.
I've met quite a few developers that really like the safari dev tools. If your not developing on mac though I don't know how good your experience is (and linux is a non starter)