Chrome's debugger is darned near a full dev environment at this point, it's just not documented all that well and a lot of the best stuff has only been added recently. You can even edit the files, run the edited code, and save the changes locally.

You know what's really good about the Chrome debugger? It's free and it's on every computer that runs Chrome. Visual Studio is neither of those. I really wish they built VS functionality into the IE debugger.

As far as showing variables, one trick I use a lot is to set a conditional breakpoint where the code to execute is `console.log(stuff), false` so that it just logs stuff but doesn't ever stop. That's also handy for "fixing" variable values without stopping.