[ryanmolden]

Does it have conditional breakpoints and tracing breakpoints? I find the latter mostly entirely eliminate the need to sprinkle printf-equivalents to follow complex flows. For full disclosure I work on VS, but not the debugger or in Javascript, and I really don't know about Chrome's dev tools, but having seen some people's approaches to debugging JS, it feels like it is in a relatively primitive state from what I am used to in other languages.

[dmethvin]

Yes and yes.

[ryanmolden]

I see conditional breakpoints, where are the tracing variety?

EDIT: Oh, I see, from your comment you are just leveraging the conditional breakpoint to ad-hoc them. That works but is a bit uglier than truly supported tracing breakpoints, and wouldn't appear to offer things like dumping the callstack to the output window or only triggering the print out only when specific conditions are met (i.e. a conditional tracing breakpoint). I suppose you could ad-hoc that as well by surrounding the print code with an if(<condition>) { print stuff }, <condition>. Works, hacky, but works I suppose.