4 ms·

> That's why we still work on Firebug To be quite frank, this is really ridiculous to me. Why in heck are there TWO separate developer tools for one browser th

> That's why we still work on Firebug To be quite frank, this is really ridiculous to me. Why in heck are there TWO separate developer tools for one browser that are both in-house? Supporting both tools means that neither one moves as quickly, and there's a ridiculous amount of confusion as to which one to use. Imagine the noobie developer that has cut their teeth on the elegant Chrome dev tools. Now they need to do some Firefox compatibility work and the first thing that happens when looking at the documentation they see both "Firefox dev tools" and "Firebug" being referenced, each with different use cases and slightly different functionality. I don't think any other issue is matters as much until you can solidify your efforts and officially support just one set of tools. Once you do that, then I think it's worth talking about all the other improvements that need to be made.

robin_reala 14y ago
Firebug isn't in house, it just has contributions from Mozilla employees.
- OmarIsmail 14y ago
  If Firebug isn't in house then I have no idea how a Mozilla employee could justify working on Firebug while their own "official" dev tools still has such a long way to go.
- chr1 14y ago
  More than 2/3 of work on firebug is done by 1 mozilla employee, and there 2-3 other people we contribute to firebug from time to time. So it's pretty much in house. IMO starting complete rewrite of firebug, in form of devtools, was very wrong. 2 years ago firebug was order of magnitude better than chrome devtools. Now it can't keep up with chrome. But firefox devtools only starts to become barely useful, If all that work have gone into improving firebug, Firefox would be ahead of chrome now.
campd 14y ago
> To be quite frank, this is really ridiculous to me. Why in heck are there TWO separate developer tools for one browser that are both in-house? I tried to clarify this in another comment: https://news.ycombinator.com/item?id=5326873 https://news.ycombinator.com/item?id=5326873 - let me know if I can clarify further.
- shuzchen 14y ago
  That still doesn't why there are two separate developer tools. Is there something that an in-house tool tied into firefox is capable of that is impossible for a plugin to achieve?

robin_reala 14y ago

Firebug isn't in house, it just has contributions from Mozilla employees.

OmarIsmail 14y ago
If Firebug isn't in house then I have no idea how a Mozilla employee could justify working on Firebug while their own "official" dev tools still has such a long way to go.
chr1 14y ago
More than 2/3 of work on firebug is done by 1 mozilla employee, and there 2-3 other people we contribute to firebug from time to time. So it's pretty much in house. IMO starting complete rewrite of firebug, in form of devtools, was very wrong. 2 years ago firebug was order of magnitude better than chrome devtools. Now it can't keep up with chrome. But firefox devtools only starts to become barely useful, If all that work have gone into improving firebug, Firefox would be ahead of chrome now.

campd 14y ago

> To be quite frank, this is really ridiculous to me. Why in heck are there TWO separate developer tools for one browser that are both in-house? I tried to clarify this in another comment: https://news.ycombinator.com/item?id=5326873 https://news.ycombinator.com/item?id=5326873 - let me know if I can clarify further.

shuzchen 14y ago
That still doesn't why there are two separate developer tools. Is there something that an in-house tool tied into firefox is capable of that is impossible for a plugin to achieve?