> The debugger I use in Chrome is a worse experience than the Visual Basic debugger I used 20 years ago. I've used both the Chrome debugger and the VB debugger

> The debugger I use in Chrome is a worse experience than the Visual Basic debugger I used 20 years ago. I've used both the Chrome debugger and the VB debugger (so you know how old I am!) and I won't speak to your comment directly, but... You have no idea how many times the Chrome JS debugger has saved my rear. :) I've been able to fix JS issues that used to take hours to debug in a few minutes since Chrome came out with its JS debugger. Firefox and IE's debuggers have gotten better - but not as good as Chrome's. And the reason I think JS debuggers aren't as good as, say, VB or Java's, is, IMHO, purely a language issue. With an interpreted language like Javascript that allows re-definition of any function or object ("prototype") or variable, I don't think the debugging tools can get any better until the language changes (which, as the author points out, is a hard sell.)