I also agree that I find FFDT unusable compared to Firebug or Chrome dev tools. I find it hard to pinpoint exactly what it is about it though.

There are lots of things, which is why it's hard to pinpoint. It's a death by thousand cut things.

The unusable console printing of objects was a big one, glad to see it's finally getting somewhat rectified.

(OTOH, Safari has taken the cake as well as the whole kitchen with the new back-asswards development tools, going from perfectly usable ones to the current utter garbage while Chrome's gets better by leaps and bounds)

(meanwhile the one bloody thing they could have, namely Xcode's awesome breakpoint actions pane, they don't integrate)

I'm guessing the browser devtools space is being subjected to the user-hostile practice of "product differentiation."

I'm sure it is, but that's not much comfort when you're forced to use that POS because it's (AFAIK) the only remote debugger for Safari/iOS, and it was previously prefectly serviceable.

I used to agree with you until Firefox 25 or so. In fact, I always tested mainly in FF (as that is my main browser) but I'd switch to chrome when I needed any sort of debugging or inspecting more complicated than reading the console.

But in the past couple revisions, I've found myself going to Chrome less and less often. Hardly ever any more with 27, and never first. Mozilla is making constant improvements and I'm quite happy with them. The debugger seems very solid to me inspector is just as good as chrome. The Chrome profiler's flame-maps are pretty awesome though.