5 ms·
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 pr
by catshirt 16y ago
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.
- ramanujan 16y agoIndeed. 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].
- catshirt 16y agofrom a brief observation, the tests in the "audits" tab seem to follow rules very similar to yslow.
- HaloZero 16y agoFireQuery is the only thing in Firebug that I can't seem to get in Chrome.
- masklinn 16y agoFirequery, YSlow, or more generally any Firebug extension not built into the Webkit Developer Tools. Also, proper stack traces.
- JonnieCache 16y agoYSlow was recently released in chrome flavour: https://chrome.google.com/extensions/detail/ninejjcohidippngpapiilnmkgllmakh https://chrome.google.com/extensions/detail/ninejjcohidippng...
- abp 16y agoGoogle Page Speed? http://code.google.com/speed/page-speed/download.html http://code.google.com/speed/page-speed/download.html
- csomar 16y agoActually 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.
- dualboot 16y agoI love Chrome but it destroys pictures with it's colour management on Mac.