Agreed. When helping other developers or QA people, it is frustrating that when they use Firefox they may not have Firebug installed and thus we can't research

Agreed. When helping other developers or QA people, it is frustrating that when they use Firefox they may not have Firebug installed and thus we can't research the issue right there. When they are usng Chrome, the damn thing is built in so I know 100% of the time that we can debug it in the browser where the issue was found. Breaking down Firebug into separate add-ons seems like a very inconvienent move. Its optimizing around the maintainer, and not the consumer - this is bad. So if a QA guy is using Firefox, worse case sceario is he downloads Firebug and restarts the browser and reproduces the issue again. In this new model, he could download the one add-on we think we need to figure out the issue, but could end up going back multiple times to install other missing components. At this point, it needs to be a "developer SDK" or "developer mode" which comes monolithically (For ease of use). If this ends up being a bundle of dependencies of smaller add-ons in the back so be it, but do not require the user to install more than one add-on to get the developer environment. Chrome did it right in my mind by shipping the whole thing with the product. This also helps garuantee that it doesn't have memory leaks, API integration problems, or other bugs which crop up when delivering what I consider basic functionality as a plug-in.