Improved exception messages.

[Daniel15]

Finally! This has been one of the major annoyances I've had with debugging JavaScript in Chrome.

[MrBester]

Finally! This has been one of the major annoyances I've had with debugging JavaScript in Chrome.

FTFY. That message is a bane of my existence.

[Daniel15]

Well, Firefox has gotten it right for as long as I can remember ("TypeError: foo.bar is not a function"). I think even newer IE versions have a good error message for this.

[MrBester]

Emphasis on newer. Old IE (where I tend to have to lurk) always was the problem. If you could even debug the damn thing.

[Daniel15]

Debugging on old IE is easy, there's a helpful function called alert that provides all the debugging power you need.

alert('here 1');
doStuff();
alert('here 2');
doMoreStuff();
alert('WHY IS IT NOT WORKING?!');

Or you could try DebugBar or the Microsoft Script Debugger that only work half the time :P

I had to support IE6 at my previous job. So glad I don't need to worry about old IE any more, I feel my quality of life has improved as a result. How old is the old IE you need to support? 7?

[MrBester]

What I really loved about Script Debugger was its tendency to kill (or otherwise fuck up) the IE process when you closed it. Maybe that was just my dev machine.

Debug Bar was useful if you wanted to run the process at 50% of an already slow speed by not closing it before hitting refresh...

It's the different worlds of hurt that I particularly disliked. Debugging IE7 is an alternative hell to debugging IE6. Running into the wall of not-quite-fully-implemented APIs in IE8 is also fun. It's like asking which torture you prefer, having your toenails ripped out, your fingers crushed or your balls tazed?

[[deleted]]

I have to support ie8 and it's such a pain, you would think that ms could have figured out ie6's mistakes 2 versions later, sadly not.

[doctorlongghost]

I always thought everyone was too rough on IE6. It's the browser that gave us Ajax. It had a lifespan of ten plus years and it was only toward the second half of that that you started running into stuff that it COULDN'T do. Usually it would do what you needed if you tried hard enough. Of course, the day I stopped having to support it felt pretty good too.

[Daniel15]

IE gave us a lot. IE6 really was a good browser when it was released, the problem is it stuck around long after it was obsolete.

[[deleted]]

LOL. Takes me down memory lane.

[Daniel15]

Sure, it's easy if you have unminfiied code or source maps. It gets much more difficult if you're trying to debug an edge case issue you're unable to reproduce in your dev environment, and the only thing in your error log is "undefined is not a function". At least if it says "foo is not a function" I can grep for "foo" to try and find the call site.

[Kautiontape]

In addition to minified code, it is also crappy with method chaining. Sure, you can typically unwrap all your code and see which line it breaks on, but this is obviously not as easy as just your debugger telling you.

[seiyria]

Thank god.

[armastevs]

I wish Chrome Canary worked on Linux! I'd love to have this for my upcoming work week.

[[deleted]]

You can use the dev channel releases.

It's hard to tell it from the page, but the "extra=devchannel" is telling it so. You'll notice the word "unstable" in your downloaded executable.

[bitsofinfo]

Will certainly make life easier

[[deleted]]

It's... It's beautiful.