It's not a big deal and I can continue to use Firebug, but the UI decisions still baffle me. Safari and Chrome display the HTML (which 90% of the time is what I'm after to begin with anyways) upon inspection with the CSS on the side. Being able to turn these off would be fine by me, but don't make me opt in every single time. Also, having the Console and other browser inspections would really take it to the next level.
Functionality notwithstanding, I really like the look and feel of it.
That's a small tweak and shouldn't diminish the overall awesomeness that is the rest of the devtools. I actually agree with you, but have found them extremely fast and usable overall.
Also, Firefox 13 (which enters beta this week) has a bunch of nice improvements including remembering whether the HTML and Style panels are open.
http://hacks.mozilla.org/2012/03/firefox-aurora-13-developer...
We're iterating at a decent pace on these tools, so keep watching. The JavaScript debugger is coming to Aurora soon and it's shaping up quite nicely. The work behind that is going to be a big win for both the new debugger UI in Firefox and ultimately for Firebug as well.
1) The Firebug team had their own priorities, development timeframes, and goals, and wasn't interested in being integrated in the core, exactly.
2) The Firebug code is .... not easy to work with. Actually trying to make any sort of significant changes to it without introducing some serious problems is pretty hard.