Hacker News new | past | comments | ask | show | jobs | submit login

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


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



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


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.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: