Can I be the only one who hates Microsoft Script Debugger as though it killed my own father? Despite Microsoft’s lead in the browser market (perhaps more likely due to IE’s bundling with Windows than IE’s actual superiority as a browser, but nevertheless) and their long-standing and well-respected support of the development community through things like Visual Basic, IIS/ASP, and .NET (both for standalone as well as web development), they are so far behind the mark in website debugging that it hurts.
I have become so accustomed to using the Firefox add-in “Firebug” to peek into JavaScript code that I am practically helpless without it. I remember a day when Microsoft Script Debugger used to open to the actual line of code with an error in it, but I guess those days are over (or it only works for debugging local ASP). Now clicking “Yes” on the script error dialog when asked “Do you wish to debug?” opens up Microsoft Script Debugger to some completely different script that isn’t even on my website. Very helpful.
Without being able to debug, I have to pepper all of my code across several libraries with alert() statements and just hope that I can figure out the state of affairs inside this twisted, illogical browser.
Thank you, Microsoft. I wouldn’t be nearly this unhappy if the browser you shoved down everyone’s throat was actually halfway decent.