2 ms·
I use Firefox’s dev tools for my work on FastMail and Topicbox (the other guy who does the most frontend work uses Chrome). Firefox’s debugger is definitely pai
by chrismorgan 8y ago
I use Firefox’s dev tools for my work on FastMail and Topicbox (the other guy who does the most frontend work uses Chrome). Firefox’s debugger is definitely painfully slow when paused and stepping, but I can’t reproduce what you say about full-browser hangs. Setting a breakpoint completes within a few hundred milliseconds (most of which is just rendering).
The fancy JSON thing: if you collapse the “JSON” expander you’ll see another, “Response payload”, which shows it as text. (If JSON is expanded, Response payload may not expand properly; that’s a bug. I haven’t reported it despite knowing about it for a while.)
Firefox has been my primary browser since 0.93, save for a year or so on Chrome when I had to run it from a USB stick and Firefox got just too slow there. Nightly has been my daily driver for most of this decade.
- kumarharsh 8y agoThe JSON thing they have fixed - I think I didn't make it explicitly clear in my comment. But it was that tree view for quite some time after the new devtools revamp. About the full browser hangs - maybe it was my own system, but I usually had Slack and Gmail open. And those tabs already ate a lot of RAM, making FF sluggish. Opening the scripting tab on my own dev site used to make the browser just get stuck. Devtools didn't use to respond either, but clicking on the close button sometimes worked, so I had to hope that I could click on the cross button without triggering the dreaded "This app has stopped responding" dialog.