However when it comes to CSS and HTML, its lagging behind Firebug.
That said, now adays I find myself in Chrome far more than Firefox simply because Javascript debugging in Chrome is fast, never crashes, and is pretty necessary if you're building an extensive rich interface app.
1. The console is a lot better. You aren't limited to the one line interpreter that Chrome provides.
2. Using console.log, and console.dir I get a colored DOM/JSON output. I can click the DOM element and it'll get me to the DOM/HTML tab. This is not available in Chrome. I can move the mouse over the DOM element and it'll be highlighted in the browser.
3. Add-ons: I use the jQuery and Cookies add-ons and they add a lot to the console. I can include jQuery with a click and it highlights the jQuery objects for me in the console. I can watch cookies changes from the console directly.
4. For the debugging tools, they are equal. For syntax coloring the JavaScript code, there is a Firebug add-on for that.
They don't link to the Elements tab though.
One of them is console.log():
(function(){
var obj = {};
console.log(obj);
obj.new_value = "hello";
console.log(obj);
})();
More details here: http://techblog.appnexus.com/2011/webkit-chrome-safari-conso...
It's not something I encounter often, but when I do, it's really obnoxious to have to work around it. I mean, it's console.log() ffs.
I switched to OSX 4 years ago and i hate to say it, but I found IE9 and IE10 debuggers (even ran in virtual machine) the be the most stable debugging tools. I encourage you to give it a try. It turns out, that we're living rather a miserable life trying to find tools that don't crash, and there are good tools out there. Too bad they are on the "alternative" operating system MS Windows is.