Firefox own developer tools won't log ajax calls in console. Firebug does. This and the fact that you need to open the settings tab to enable preserve log are my problems with Firefox tools keeping me on firebug.
Personally I've switched back to dev tools in the developer edition, mostly because the ability to see which elements have events attached from the markup view is very useful.
One advantage is that there are plugins, like YSlow from Yahoo, that are available for Firebug. Though the article notes that plugins don't currently work with the Firebug 3 alpha.
YSlow is pretty useful, both as a developer and when attempting to demonstrate potential problems with a site's performance to others in an objective way.
Besides: a plugin with its own plugins is just cool.
I think Firefox Dev Tools may have reached parity with Firebug. Up until recently (~3 months), Firebug was superior in network, more informative in console when using console.log for objects, resizing, etc. Still, Firebug does have add-ons
[+] [-] kyriakos|11 years ago|reply
[+] [-] nathanstitt|11 years ago|reply
I'm attempting to find time to assist with it, but haven't thus far. Perhaps throwing it out here will bring in additional assistance
[+] [-] robbyt|11 years ago|reply
[+] [-] eterm|11 years ago|reply
[+] [-] harpb|11 years ago|reply
[+] [-] makmanalp|11 years ago|reply
[+] [-] __david__|11 years ago|reply
[+] [-] findjashua|11 years ago|reply
[+] [-] DrinkWater|11 years ago|reply
[+] [-] JohnBooty|11 years ago|reply
YSlow is pretty useful, both as a developer and when attempting to demonstrate potential problems with a site's performance to others in an objective way.
Besides: a plugin with its own plugins is just cool.
[+] [-] arenaninja|11 years ago|reply
[+] [-] Fuxy|11 years ago|reply
I honestly wish they did since there are very few features I would miss from Firebug itself but the plugins add very useful features.
[+] [-] ep103|11 years ago|reply