I like the search feature in Firebug. Being able to search across all scripts/nodes/stylesheets is rad. Is Chrome Dev Tools' search that good yet? Every time I am working with another dev and want to search for a symbol, I tell the other devs to switch to Firefox/Firebug because Chrome Dev Tools is a mystery of hunting and pecking when it comes to search. (Google is not the best at something-something search??) I cannot understand why other devs are so happy with Chrome.
The Chrome timeline is rad when it comes to performance tuning, and maybe a lot of devs are light on the JS and heavy on the CSS. I jump into Chrome, briefly, whenever I want to tune performance.
All of the dev tools have quirks, bugs, and dumb UI usability issues, but when I want to work with a large codebase (which is every day of my life), I find Firebug works the best.
Chrome Dev Tools have had this for some time. On OSX Command-Option-F. Or, click the 'Search' tab in the console.
I haven't really found anything Firebug does that Chrome doesn't, and tons of stuff Chrome does that others don't, like debugging Web Workers, or awesome profiling tools for both JS CPU/HEAP, as well as internal browser profiling. Chrome Tracing is unparalleled.
Command-Option-F! I learn something new every day, thanks!
I've always gotten tripped up by the fact that Command-F pulls up a local file Find toolbar when I've focused a JavaScript source page. I assumed that was the extent of the Find capabilities Chrome offered. I'm 51% angry and 49% embarrassed that I never knew this! :)
Agreed the Web Workers debugger in Chrome is very advanced and as I recall they had that available straight away when the Web Workers feature was first released.
I think the Firefox/Firebug guys have only just added javascript console output for web workers in Firefox 30 and the debugger protocol for web workers is still in development.
I agree that Chrome's developer tool suite is more comprehensive than other browsers. For my day to day development tasks, looking at network calls, inspecting html and debugging CSS/JavaScript, Firefox+Firebug is still the most user friendly and accessible to me.
The Chrome timeline is rad when it comes to performance tuning, and maybe a lot of devs are light on the JS and heavy on the CSS. I jump into Chrome, briefly, whenever I want to tune performance.
All of the dev tools have quirks, bugs, and dumb UI usability issues, but when I want to work with a large codebase (which is every day of my life), I find Firebug works the best.