Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Firebug 2.0

blog.getfirebug.com

Post reply on HN
Print view View original

61–70 of 123 posts

Re: Firebug 2.0

#61

Post by batuhanicoz »

gkoberger wrote: post #16

I 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 thing I miss the most is the inline display of AJAX call responses

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).

Re: Firebug 2.0

#62

Post by dfc »

joewalker wrote: post #46
dfc wrote: post #33

Earlier quoted context omitted.

I hate the fact that the close window/dialog button for the devtools is on the left hand side when every other plugin puts this on the right hand side. I am not an every day user of FF's built in devtools so it is not something that I am accustomed to. Despite firebug's performance troubles when I go to select devtools or firebug I usually opt for firebug simply because the close button drives me nuts.

We moved the button and a number of the tabs in Firefox devtools to be more like the order in Firebug and Chrome devtools. Here's a screenshot from current Nightly: https://i.imgur.com/EmVIZYO.png

Nice. I am running the aurora release on this machine so it is still on the left. I cant wait to have button sanity. Thank you for your efforts.

http://i.imgur.com/W9Z5jBJ.png

Re: Firebug 2.0

#63

Post by interurban »

batuhanicoz wrote: post #61
gkoberger wrote: post #16

I 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 thing I miss the most is the inline display of AJAX call responses 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).

You can enable XHR logging in the settings panel as well.

Re: Firebug 2.0

#64

Post by darkhorn »

andrethegiant wrote: post #8
ep103 wrote: post #2

Still 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?

It doesn't run on PCs.

Re: Firebug 2.0

#66

Post by cromwellian »

EdSharkey wrote: post #35
ep103 wrote: post #2

Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.

I like the search feature in Firebug. Being able to search across all scripts/nodes/stylesheets is rad. Is Chrome Dev Tools' search that good yet? Every time I am working with another dev and want to search for a symbol, I tell the other devs to switch to Firefox/Firebug because Chrome Dev Tools is a mystery of hunting and pecking when it comes to search. (Google is not the best at something-something search??) I can…

Chrome Dev Tools have had this for some time. On OSX Command-Option-F. Or, click the 'Search' tab in the console.

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.

Re: Firebug 2.0

#67

Post by chowells »

Sindrome wrote: post #15

I 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.

If they don't know what Firebug is, they're not versed in the tools of the trade. You should consider that to be a very serious red flag about working with them.

(Edited for tone)

Re: Firebug 2.0

#68

Post by lomnakkus »

ben336 wrote: post #5
ep103 wrote: post #2

Still the best developer toolset, on any browser. Unarguably once its combined with FF native tools, and the webdevtoolbar.

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.

One thing that I found indicative of the "depth" of Firebug is the very simple context menu item when you right-click a URL in the Network tab: "Copy as Curl command" (the text may read differently, this is from memory). It creates a clipboard entry which contains a "curl" command line with all the cookie/header/etc. data that would be sent from your browser if you were to request that URL (via Ajax or whatever). You paste that into your terminal and you can keep retrying indefinitely without having to click/interact with the web page at all. Hugely useful if you're debugging the server side of a client->server interaction.

Re: Firebug 2.0

#69

Post by wnevets »

I used to use firebug religiously, however I've been using chrome's tools for the past two years and haven't felt a need to go back.

Re: Firebug 2.0

#70

Post by mmastrac »

Pretty-printing: awesome! Unfortunately it's a little buggy when setting breakpoints. I tested it using the minified version of jquery on the Mozilla pages and it quickly went out of sync while stepping into a function.

I'd consider dropping Chrome for this feature, as Chrome broke pretty printing in some cases in a recent update.

Post reply on HN