[illumen]

Yeah, firebug still has quite a lot of polish compared to the others.

Perhaps it has to do with the contributors being expert UI developers, and firebug developers second. Whereas the other tools are mostly developed by employees who do full time dev tool development, but not so much work using the tools.

But I know others mostly prefer chrome tools. The same people often get stuck in firebug or in IE dev tools.

Anyway... GREAT WORK FIREBUG TEAM! xo

[dubcanada]

I fail to see how Firebug has a better UI then WebKit Developer Tools?

As far as I am concerned they are the same in that regard. And since both of those tools are not built by "developers", but by "frontend engineers" it doesn't really matter.

I spent like 15 minutes trying to figure out how to attach Firebug to the browser window. Only to find out that the upward pointing arrow in a gray circle means attach to browser window. On WebKit I click an icon that looks like a browser window with developer tools.

The resources tab in WebKit is ten times better then the mishmash of CSS/Script/Net/Cookies tabs all spread out.

Anyways that is just my opinion, and as far as I am concerned Dragonfly was the best.

[yogo]

I guess it comes down to personal preference but I've always thought Firebug beats Elements and Resources in Chrome. It is much faster to filter with tabs than digging through a tree IMO.

[actionscripted]

Think what s/he's saying is that it helps that they use their own tools for UI dev versus those who hammer on the browser and made comparable tools, not that Firebug has a better UI.

[dubcanada]

That's fine, but I think it's a bit far fetched to say that the people who work on WebKit/Blink developer tools don't use the developer tools.

[paulirish]

It's true.. the Chrome DevTools are a webapp, and the engineers behind it use the DevTools _on_ the DevTools as their primary means of development. (Enter inception joke here). From what I can tell, the same is true with the Safari Inspector and the IE F12 Tools.