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

71–80 of 123 posts

Re: Firebug 2.0

#71

Post by jrochkind1 »

lomnakkus wrote: post #68
ben336 wrote: post #5

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

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…

Chrome dev tools has that too these days. Copy as curl.

Re: Firebug 2.0

#73

Post by razorshine »

this was one of the original must have extensions in the early days of FF.. haven't been back though since the browsers integrated them in by default. not sure why i would?

Re: Firebug 2.0

#74

Post by mmuro »

_puk wrote: post #30
andrethegiant wrote: post #8

Earlier quoted context omitted.

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?

Now that Chrome and Safari inspectors have started to diverge significantly I find the Chrome inspector far superior. It just feels like more time has been invested in it. 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?

Yes, Safari supports source maps (has for a while).

Re: Firebug 2.0

#75

Post by doque »

Firebug is still the best tool set on any browser. I still recall the times where you had to debug IE using alert() statements without any sort of debugger.

Re: Firebug 2.0

#76

Post by tinco »

21echoes wrote: post #21
Kiro wrote: post #14

Earlier quoted context omitted.

I find the Firefox dev tools very inferior to Chrome dev tools, missing a lot of "must have" features.

such as? not disagreeing, just wondering what you consider "must have" features that Firefox currently lacks.

Not that I hate the Firefox devtools, but at the moment I'm using Chrome because there's no way to disable the caching of XMLHTTPRequests in Firefox, and I'm developing a Google Polymer app.

Re: Firebug 2.0

#77

Post by EdSharkey »

cromwellian wrote: post #66
EdSharkey wrote: post #35

Earlier quoted context omitted.

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.

Command-Option-F! I learn something new every day, thanks!

I've always gotten tripped up by the fact that Command-F pulls up a local file Find toolbar when I've focused a JavaScript source page. I assumed that was the extent of the Find capabilities Chrome offered. I'm 51% angry and 49% embarrassed that I never knew this! :)

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 think the Firefox/Firebug guys have only just added javascript console output for web workers in Firefox 30 and the debugger protocol for web workers is still in development.

I agree that Chrome's developer tool suite is more comprehensive than other browsers. For my day to day development tasks, looking at network calls, inspecting html and debugging CSS/JavaScript, Firefox+Firebug is still the most user friendly and accessible to me.

Re: Firebug 2.0

#78

Post by rsl7 »

Viper007Bond wrote: post #7
JoshTriplett wrote: post #3

I used to use Firebug extensively. These days, the built-in Firefox developer tools seem to cover everything I need.

Same here. Can any current Firebug users comment as to what they like about it over the built-in tools?

I like the built-in tools, but the two things I like in Firebug and use extensively are the DOM inspector and pretty printing JSON results in the Net panel for API calls.

Re: Firebug 2.0

#80

Post by tambourine_man »

sroussey wrote: post #49
tambourine_man wrote: post #41

The first thing I see is the glaring lack of anti-alias on the Firebug logo. It looks like a variant of Open Sans, if anyone would point me to it, I can fix it.

https://github.com/firebug/firebug/tree/master/extension

I don't see either the font file or the vector artwork in this distribution
Post reply on HN