Hacker News Reader

Comment by random42 | Hacker News Reader

Unfortunately, for me its a catch22 situation. I hate firefox because its slow, and love/depend on firefox, because of firebug (which apparently makes firefox slow.)

View on HN

i resisted switching to chrome for months because i thought the chrome inspector was inferior to firebug, but i got used to it after forcing myself to switch primarily to chrome. now i find it's actually superior in many ways.

Indeed. Little things like proper emacs keybindings in the JS terminal (Ctrl-P for previous line = lifesaver!) make Chrome's inspector preferable. Haven't needed to go back except for the YSlow/Firebug integration [probably a Chrome plugin for that as well].

from a brief observation, the tests in the "audits" tab seem to follow rules very similar to yslow.

FireQuery is the only thing in Firebug that I can't seem to get in Chrome.

Firequery, YSlow, or more generally any Firebug extension not built into the Webkit Developer Tools.

Also, proper stack traces.

YSlow was recently released in chrome flavour:

https://chrome.google.com/extensions/detail/ninejjcohidippng...

Google Page Speed?

http://code.google.com/speed/page-speed/download.html

Actually FireBug sucks for inspecting elements. I prefer Chrome and Stylizer (CSS). FireBug is good in JavaScript (very good) and the browsing of the DOM. I like it.

I love Chrome but it destroys pictures with it's colour management on Mac.

I gladly take the hit that FireBug causes, same reason. The slightly longer startup time doesn't bother me (yet).

Also, I can't stand webbrowsing on an installation which doesn't have some form of adblocking. What a difference! I find ads horribly distracting, especially when they have flashing animations.

Have you tried Chrome's inspect element?

I use firebug to trace the HTTP requests, mainly. I know there are alternatives (for both Chrome and Firefox), but none of them compare to firebug. May be its because of my comfort/acquaintance level with firebug.

Used to think like you, but chrome's network tab (in the developer tools) has really come a long way

You are probably correct. But you know, dev. tools are like IDEs/Editors. Once you get settled with one, there is a level of comfort with the tool, you dont get with others.

if were going to talk about HTTP monitor alternatives please dont forget to talk about Charles. In many ways i prefer it to built in browser monitors because it is designed to capture any requests regardless of source.

Chrome and Opera have a Firebug alternative built into them.

Not only does it slow down Fx start up times, but also new window creation times, even when it's not active ('off' state). Disabling it completely in add-ons restores performance. On my Mac this means seemingly instant vs noticeable delay, and that bothers me.

Use multiple profiles, one for everyday browsing and one for Firebug.

Thats what I do (well, sort of). just that I have to keep another browser installed.

                           --Written at my Google Chrome.

Reply on news.ycombinator.com