Well, I haven't done any specific comparisons, they just SEEM to be faster. It could just be that they are pretty much the same and I just use Firebug more. One case where I've seen Firebug slow down the page significantly is when running decodeURIComponent on a several thousand characters long string... But it is possible that the other in-browser debuggers would have the same problem, I don't know.
The thing with those in WebKit and Opera is that it seems like they are always running in the background. WebKit, for example, has the Activity Monitor (basically the "Net" tab) and it is always watching for traffic. Additionally, you can see traffic for every site you have open in the same window. On Aug 17, 4:12 pm, johnjbarton <[email protected]> wrote: > On Aug 17, 2:04 pm, sir_brizz <[email protected]> wrote: > > > I think all that ever needed to be said about how far backwards > > Firebug went in usability and interface design has been said numerous > > times and it isn't going to be changed. I'm of the opinion that, while > > Firebug was originally (1.0-1.2) the standard for in-browser > > javascript and event debugging, since then the debuggers in WebKit and > > Opera have far eclipsed it in terms of speed, user experience, > > usability, and design. They have lots of nice features that are not > > implemented in Firebug, they work in (what seems to be) more sensible > > way, and they are extremely fast. > > I would be interested in specific features and in any reports on > aspects of Firebug which seem too slow. > > jjb --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/firebug?hl=en -~----------~----~----~----~------~----~------~--~---
