3
User
Recs.
Recs.
20
Updates
Last
Updated
Updated
Activity
5 Options
SpecsUpdate
Pros
Know any positive aspects of this option?
Cons
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).
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.
Know any negative aspects of this option?
Recommendations
Visual Studio Code
3 years ago
Con
The autocomplete and code check is not as powerful as the one on WebStormCon
Embedded Git isn't powerful enoughCon
Project search limits resultsCon
Very bad auto importCon
GeneralizedCon
Memory hogCon
Poor error fix suggestionsCon
A "me too" offering from MS, far behind other well established editors that it attempts to cloneCon
Slow launch timeCon
Emmet plugin often fails on even simple p tags