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.
I read that Firebug 2 now uses the newer JSDBG2 API of recent Firefox, so there should be no performance problems as there were with Firebug 1.x in recent Firefox versions.
If I understood correctly, you can have this on Chrome. In Chrome JS Console, do a right click in an empty space, and select "Log XMLHTTPRequests" (or it was something similar).
To see the actual response, you have to click the URL, which takes you to the Network panel. Then you have to find the request on the Network panel (no clue why it doesn't deep link to the correct tab), then click Response.
Probably not 100% what you wanted, but they're really handy for sketching out code fragments.
Much of the new JS that I write these days starts as a scratchpad that I evolve over many iterations, right in the browser.
See http://fitzgeraldnick.com/weblog/54/ for some implementation details.
Happily, memory profiling tools designed for use by web devs are being actively worked on.
There are just a number of really small issues other than those that when you add them up, make the dev toolbar a lot less useful than Chrome. That said, I like Firefox the browser much better than Chrome.
Starting in Firefox 31, the console will display a full stack trace for errors
If you're using nightly you already have had a lot of features like this for a while.
I find the dev tools in nightly a lot more useful than those in chrome and I prefer the way the dev tools are layed out in nightly. I also like the responsive design view, GCLI, and the eyedropper.
Mobile development with Firefox is a pain compared to Chrome.
This way you can open as many firefox as you want.
Can any current Firebug users comment as to what they like about it over the built-in tools?
I'll give the new firebug a try.
Ever since FF tools added the "clear" buttons in the Console and Network tab, they won me over
(Edited for tone)
Only issue I have is the fact it changes more or less every release, leading to a day or so of re-learning how to do certain tasks.
Does Safari support source-maps yet?
It has a platform limitation.
Safari does not work on anything but MacOS and iOS, so developing for it requires additional testing.
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)
The Chrome timeline is rad when it comes to performance tuning, and maybe a lot of devs are light on the JS and heavy on the CSS. I jump into Chrome, briefly, whenever I want to tune performance.
All of the dev tools have quirks, bugs, and dumb UI usability issues, but when I want to work with a large codebase (which is every day of my life), I find Firebug works the best.
I haven't really found anything Firebug does that Chrome doesn't, and tons of stuff Chrome does that others don't, like debugging Web Workers, or awesome profiling tools for both JS CPU/HEAP, as well as internal browser profiling. Chrome Tracing is unparalleled.
Agreed the Web Workers debugger in Chrome is very advanced and as I recall they had that available straight away when the Web Workers feature was first released.
I agree with you on webdevtoolbar, that is a fantastic tool for inspecting/altering aspects of the page. I wish webdevtoolbar had user agent tools. I have to run another plugin to give me user agent spoofing.
@Firebug 2 devs: Please make the JSON preview table-rows-width adjustable - the JSON "key" row-width is too wide!
@Firefox DevTools devs: please finally fix support your JSON preview (see above)
It looks like a variant of Open Sans, if anyone would point me to it, I can fix it.
Look for firebugBig.png and firebugSmall.svg. I _think_ those are the files.
I'd consider dropping Chrome for this feature, as Chrome broke pretty printing in some cases in a recent update.
I prefer Firebug over other dev tools but it is useless without this feature.
Entering safe mode, uninstalling the existing version and attempting to close all tabs related to Firebug seemed to fix the problem.
So you may want to try removing your existing Firebug before installing.
With the newer debugging interface it seems like firebug can work and the browser can be fast.
about:config -> devtools.inspector.enabled -> false
In general, in the open source landscape, people work on whatever they want to work on, not on what somebody promises.
Can I inspect Websockets with Firebug?
Or maybe newer Firefox versions ?
It wasn't ready in time to coincide with Firefox 30 (which removed our default debugger interface, so our release had to go out).
You can star the issue to get updated on progress.