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

Firebug Metamorphosis

blog.getfirebug.com

Post reply on HN
Print view View original

21–30 of 79 posts

Re: Firebug Metamorphosis

#21

Post by Timmy_C »

erikpukinskis wrote: post #11
dboyd wrote: post #9

With no doubt, the Firebug team can take credit for changing the world of Web development. These guys aren't giving themselves enough credit. IMO, they can take credit for advancing the world of Web development. While the other development tools are (quickly) catching up, firebug is still leading the pack.

I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.

I do a lot of Omniture and DoubleClick analytics development and I find that Firebug plugins like Omnibug are irreplaceable. Is there an equivalent debugging tool for Chrome?

Re: Firebug Metamorphosis

#22

Post by masklinn »

rottencupcakes wrote: post #19
erikpukinskis wrote: post #11

Earlier quoted context omitted.

I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.

Personally I browse in Chrome, but the second I start debugging JS/AJAX i'll open Firefox and use that. It's 10x slower, it has Memory leaks up the wazoo, but firebug blows chrome's debugger out of the water.

> but firebug blows chrome's debugger out of the water.

Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?

Re: Firebug Metamorphosis

#23

Post by themanr »

I would love to see a JavaScript debugger that could break to something like an ipython shell. It's the one thing I really miss moving from server side to client side debugging.

Re: Firebug Metamorphosis

#24

Post by masklinn »

Timmy_C wrote: post #21
erikpukinskis wrote: post #11

Earlier quoted context omitted.

I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.

I do a lot of Omniture and DoubleClick analytics development and I find that Firebug plugins like Omnibug are irreplaceable. Is there an equivalent debugging tool for Chrome?

Not that I know of: the webkit dev tools aren't externally pluggable (if they are I missed how, but since Chrome and Safari have different plugin architectures I don't see how that would work), so third-parties (to both the browser and the tools, but for Webkit browsers they're kind-of merged) can not extend the tools aside from getting patches merged into mainline.

Re: Firebug Metamorphosis

#26

Post by rhodimus »

masklinn wrote: post #8
rhodimus wrote: post #4

Earlier quoted context omitted.

I can only speak for the Chrome/Safari WebInspector, and they're good, but I find myself going back to Firebug if I have to do any serious debugging - personally I find there to be a big step up in usability with Firebug meaning I can work faster. It'll be interesting to see what happens to development tools when Firebug goes cross-browser.

> I find myself going back to Firebug if I have to do any serious debugging Why? What difference do you see between the browsers debugging-wise?

> Why? What difference do you see between the browsers debugging-wise?

Feature-wise, very little. But as I said - I do find I can work faster with Firebug - I much prefer the the DOM inspector (one click node editing, css editing, the fact that it live updates the DOM as it is changed via any JS running on the page) and the console (DOM/JS object inspection and having XHR logging in the console itself and not on another tab). Plugins such as FireQuery also make a difference for my needs.

Re: Firebug Metamorphosis

#27

Post by guelo »

masklinn wrote: post #18
erikpukinskis wrote: post #11

Earlier quoted context omitted.

I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.

> and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome. Obscene? On OSX with Firefox 3.6 and Chrome 6, the difference is about the height of Firefox's tabs on top, with the web developer toolbar enabled. Disable/hide the web dev toolbar and the difference is a few pixels in favor of Chrome. nb: status bar and bookmarks toolbar disabled in Firefox.

I just measured a 50px difference in my configuration, that is including Firefox's Status bar at the bottom and not including Chrome's 20px fly-out link hover thing at the bottom left. Of course you can completely change Firefox around if you you want.

Re: Firebug Metamorphosis

#28

Post by pornel »

It would be cool if all inspectors' front-ends and back-ends became interchangeable.

Opera Dragonfly goes in that direction. It's open-sourced (http://bitbucket.org/scope/dragonfly-stp-1/) and uses documented protocol for communication with browser core:

http://dragonfly.opera.com/app/scope-interface/

Recently Dragonfly has been made compatible with Chrome, debugging Opera remotely:

http://twitpic.com/30ul4b

Re: Firebug Metamorphosis

#29

Post by carbon8 »

erikpukinskis wrote: post #11
dboyd wrote: post #9

With no doubt, the Firebug team can take credit for changing the world of Web development. These guys aren't giving themselves enough credit. IMO, they can take credit for advancing the world of Web development. While the other development tools are (quickly) catching up, firebug is still leading the pack.

I've pretty happily switched to Chrome, which seems to do everything I used to ask Firebug to do. Although honestly I no longer use Firebug because I no longer use Firefox, and I no longer use Firefox because it takes up an obscene amount of vertical real estate compared to Chrome.

The webkit nightlies tend to have more features. There is still one behavior that frustrates me every time I use the webkit tools, though: clicking on an asset link (eg, to a javascript file) brings up the resource tracker rather than the file.

Re: Firebug Metamorphosis

#30

Post by nowarninglabel »

masklinn wrote: post #22
rottencupcakes wrote: post #19

Earlier quoted context omitted.

Personally I browse in Chrome, but the second I start debugging JS/AJAX i'll open Firefox and use that. It's 10x slower, it has Memory leaks up the wazoo, but firebug blows chrome's debugger out of the water.

> but firebug blows chrome's debugger out of the water. Could you please describes the ways in which it "blows chrome's debugger" [actually the Webkit Development Tools, it's been much more than a debugger for quite a long time) "out of the water" in your opinion?

Yeah, I'd also like to see an analysis of this. I used to be an automatic 'switch to Firefox for debugging' user, but I find that the Chrome developer tools are now pretty sufficient.
Post reply on HN