Live data from Hacker News

Firebug Metamorphosis

blog.getfirebug.com

41–50 of 79 posts

Re: Firebug Metamorphosis

#41

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.

My Firefox takes up less vertical real estate than Chrome. I use Tiny Menu, customize the toolbars to put everything into the menu bar, and use Tree-Style Tabs to show the tabs vertically along the right side. The best option I have at work is Chrome, and having the tabs along the top is much less usable compared to Tree-Style Tabs.

It's subjective. I tried and hated tree style tabs.

I prefer Chrome these days but Firefox and Safari are still up there, and also fast[1]. It's just nice to have a variety of good browsers to choose from.

[1] http://arewefastyet.com (doesn't say "no" anymore)

Re: Firebug Metamorphosis

#42
post #23

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.

check out mozrepl and mozrepl mode.

Re: Firebug Metamorphosis

#43

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?

There is no equivalent to the Firefox JavaScript console, especially when you add the jQuery plugin to it. Chrome console sucks. Their DOM explorer is superior in some ways, though.

Re: Firebug Metamorphosis

#44
Has someone looked at the Web Console features ?https://developer.mozilla.org/en/Using_the_Web_Console

It is just a simple console like Firebug Lite. Even the site says "The Web Console won't replace more advanced debugging tools like Firebug", so why is the Firebug team so worried about it?

Firebug is a great tool for Mozilla browsers and I feel that considering porting Firebug to other browsers could be a difficult goal for the project.

Re: Firebug Metamorphosis

#45
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.

Chrome is also my primary browser, but I wanted to point out a discovery I made today:

The Chromifox Extreme[1] Firefox theme in combination with its bundled helper extension completely negates the vertical pixel space waste in Firefox vs. Chrome, at least in Mac OS.

I'm actually using the carbon variant[2] in combination with the Omnibar extension[3] to combine the URL and search bars.

[1] https://addons.mozilla.org/en-US/firefox/addon/10674/

[2] https://addons.mozilla.org/en-US/firefox/addon/10883/

[3] https://addons.mozilla.org/en-US/firefox/addon/8823/

Re: Firebug Metamorphosis

#46
post #29

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.

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.

There are a lot of tiny little details like that, that in sum make webkit's inspector not as a good experience as firebug

Re: Firebug Metamorphosis

#47
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.

Grab the "Chromifox Extreme" and "Hide Menubar" extensions for FF 3.6. These will give almost the exact same vertical screen space.

Re: Firebug Metamorphosis

#48

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.

Funny story -- if you remove Firebug, Firefox stops being so slow and leaking memory.

Re: Firebug Metamorphosis

#49

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.

The moment you enable the javascript features of firebug, the browser disables its jit tracing leading to a slower experience. You are a victim of your own usecase.
Post reply on HN