ETA: yes it has debuggers for some languages as well, though none that I am using at the moment.
https://marketplace.visualstudio.com/vscode/Debuggers
You can set breakpoints, check out the call stack, and inspect local variables.
But after using VS Code for a while now I'm pretty sure I'll keep using it, at least for Node.js development. The IntelliSense support through TypeScript definitions, the out-of-the-box support for what I consider essentials (linting, task running, emmett, etc.), and perhaps most importantly the built-in debugger make my life significantly easier.
I enjoyed working with node-inspector, but the debugging in VS Code is a lot more convenient (mostly).
To be fair, for non-node development I'd say VS Code is not yet good enough to replace Sublime Text, but that might change when enough plugins and features have been added.
What it boils down to for me is that VS Code somehow seems to be optimized exactly for my workflow. It doesn't have tons of buttons and interface elements that I don't need (as many IDE's do), and it isn't slow. But on the other hand it offers very sensible defaults that other editors such as Atom and Sublime don't have. On both those editors I've had some issues with setting up linting, debugging, IntelliSense, and a few misc. other things. The main reason for that, I suppose, is that they're all plugins developed by different people. I like how these just come with VS Code and work right away.
I'm rather baffled that I'm saying all this, considering my general aversion of using Microsoft products (even if this is based on the past). But it is what it is. VS Code is a huge timesaver for me, and (mostly) hits the sweet spot between plain, fast editor and IDE.
But please give me Vim support ASAP :).
Apart from an occasional restart required it has been pretty solid. Performance(autocompletion etc) is very good and for TypeScript development, VSCode is pretty feature complete...
A lot of people expect a "real IDE" to have a lot of fancy, specific, semi-proprietary features, but what I believe VSC is providing great editing capabilities and offloading everything else to good task managers (and now, extensions). A lot that you can do in "real IDEs" (like building your project) can be handled by Gulp, Grunt, or other runners in a more or less independent way. I actually prefer it this way now, regardless of the IDE I use - that allows my projects to be independent of the IDE.
To me, where VSC shines is really in editing comfort, be it with the super fast typing response (really!), or with the Git integration, or with how it handles work space for opened files. It looks like it is supposed to be uncomplicated.
How do you measure the typing response? Do you have a speed camera hooked up or something!?
I think they optimized the way code drawing is done in such a way that it just happens with the least amount of time possible between typing and drawing. The end result is the same as if you typed anywhere else, but because the response is cut by, say, 16ms, it just feels fast. I remember the first time I tried VSC - I almost felt like the letters where coming out from under the cursor ahead of time! It was a weird moment.
The counterpoint is IntelliJ. It's not a slow IDE (I used Eclipse before so that'd be unfair to say), but maybe it has a couple of frames too many before drawing what's typed, so it feels like it's lagging in comparison. Maybe why they're making it a point of future releases[1] to reduce any typing lag.
[1] http://blog.jetbrains.com/idea/2015/08/experimental-zero-lat...
- I like the 2-pane integrated Git panel.
I'm not properly coding in it yet.