Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 2
    For basic debugging, the IE8 debugger has suited most of my needs. However, if you are doing any sort of performance testing, you will quickly find IE lacking. I had a project recently that utilized some heavy javascript, and we really needed to trim things down for inferior systems, as we were running into the dreaded "unresponsive script error". Firebug was invaluable in this instance, because I was able to run the console.profile() method to figure out where all of my time was being spent. Commented Jun 12, 2009 at 19:44
  • 1
    The IE8 debugger also has a profile feature (albeit not as graphical as FireBug) that provides call tree, call count and time spent on each method. I've found this adequate in isolating which JS code is taking too long. Commented Jun 12, 2009 at 19:59