Resumen

Resumen
The proliferation of sophisticated AJAX applications has permanently changed the design center of the JavaScript environment. Scripts are large and complex. Now, at best, script execution failure results in an awkward experience. At worst, the application ceases to work or corrupts server-side state. The severity of the problem depends on the nature of the debugging environment. When a bug is encountered in production, enough information must be preserved such that the root cause can be accurately determined, and this information must be made available in a form that can be easily transported from the user to engineering. Depending on the browser, JavaScript has a rich set of tools for identifying the bugs at the root of problems during the development phase. Sadly, JavaScript support for stack traces is sorely lacking. The browsers that do support stack traces make them available only via thrown exceptions, and most browsers don't provide them at all. A window.onexception() handler that's passed as an exception object would be a welcome addition.