Recs.
Updated
SpecsUpdate
Pros
Pro Excellent integration with VisualStudio projects
You can easily switch from VisualStudio to VSCode to work on your web projects in a lighter environment if you, for example, just want to work on your interface design or anything that doesn't require a complex IDE, and VSCode won't do anything strange or affect your project's builds in any way.
Cons
Con Telemetry enabled by default
Visual Studio Code collects usage data and sends it to Microsoft, although this telemetry reporting can be disabled. The data is shared among Microsoft-controlled affiliates and subsidiaries and with law enforcement per the privacy statement. Source: Visual Studio Code
Con Have no good default js style analyzer
In WebStorm there is analyzer that checks for warnings and highlight this in yellow, here you cannot find or add it even with plugins. It is possible to have it as errors with linter but while you are actively changing file that's not very nice.
Con Embedded Git isn't powerful enough
You can do nothing but to track changes, stage them and commit. No history, visualization, rebasing or cherry-picking – these things are left to git console or external git client.
Con File search is extremely slow
It's absolutely not possible to use this tool with big projects given how long it takes to search for files.
Con Memory hog
Allegedly, VS Code is "lightweight". Yet, running multiple instances of it at once, you may get many "out of memory" messages from Windows despite 16 GB RAM. (While of course also running other things. The point is the comparison with some other IDEs/editors where running them alongside the same number of other applications doesn't cause Windows to run out of memory)
Recommendations
Comments
Flagged Pros + Cons
Pro Active development
It's really nice to see how the code editor evolves. Every month there is a new version with great communication of new features and changes.