When comparing Visual Studio Code vs IntelliJ Rust, the Slant community recommends IntelliJ Rust for most people. In the question“What are the best editors/IDEs for Rust?” IntelliJ Rust is ranked 1st while Visual Studio Code is ranked 2nd.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Extendable through plug-ins
Visual Studio Code comes fairly complete out of the box, but there are many plug-ins available to extend its functionality.
Pro TypeScript integration
There is very solid TypeScript integration in Visual Studio Code. Both are developed by Microsoft and VSC itself is written in TypeScript.
Pro Integrated debugging
VSC includes debugging tools for Node.js, TypeScript, and JavaScript.
Pro Ready to use out of the box
You don't need to configure and add plugins before being productive. However, you can add plugins if needed but for the basics you're well covered.
Pro Integrated terminal
There's no need to press alt+tab to go to a terminal: it is directly integrated into the editor. Shift+~
is a handy hotkey to toggle the integrated terminal.
Pro Great performance
For a 'wrapped' web-based application, Visual Studio Code performs very well.
Pro Libre/open source
Released under the MIT License.
Pro Fast and powerful
VS-Code has the speed of Sublime and the power of WebStorm. Perhaps this is the best software that Microsoft has ever created.
Pro JavaScript IntelliSense support
JavaScript IntelliSense allows Visual Studio Code to provide you with useful hints and auto-completion features while you code.
Pro Embedded Git control
Visual Studio Code has integrated Git control, guaranteeing speed, data integrity, and support for distributed, non-linear workflows.
Pro Updated frequently
There's a new release of Visual Studio Code every month. If you are one of the insiders then releases are daily.
Pro ESLint integration
ESLint integrates great. You can define your rules trough .eslintrc.* as usual and vs code will autofix your code on save. So your code is always in style.
Pro Extensions (aka plugins) are written in JavaScript
Extensions are written in either Typescript or JavaScript.
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.
Pro Integrated task runners
Task runners display lists of available tasks and performing these tasks is as simple as a click of the mouse.
Pro It has gotten really good
All it takes is one stop for all the features many people need.
Pro Custom snippets support
Snippets are templates that will insert text for you and adapt it to their context, and in VSC they are highly customizable.
Pro Huge community behind it
The ease of getting assistance and finding tutorials is increasing as the community grows.
Pro JS typechecking
It leverages TypeScript compiler functionality to statically type check JS (type inference, JSDoc types) with "javascript.implicitProjectConfig.checkJs": true
option.
Pro Python support
Excellent Python plugin, originally created by Don Jayamanne, now hired by Microsoft to extend and maintain the extension.
Pro Good support for new Emmet syntax
Pro High fidelity C# plugin
The Omnisharp plugin is very powerful providing full sln, csproj, and project.json support.
Pro Support RTL languages
It supports pretty web rtl languages like arabic languages when most of other editors don't support it.
Pro Inline definition picking and usages finding
These features allow you to have a glance at code without opening it as a whole in a separate tab. Moreover, editing is allowed.
Pro A fully featured IDE
Pro Constantly being updated
Pro Full power of IDEA engine
This plugin uses big part of Intellij IDEA features, including advanced code analysis and refactoring.
Pro Free/Libre (MIT)
Currently
Pro Many users
Has more users than the average plugin.
Pro The best VI shortcut plugin
For those that favor VI shortcuts, you can do nearly everything in IntelliJ that you would do in a VIM editor. Almost no conflicts out of the box, and those that are in conflict are easily resolved.
Pro Built-in user friendly terminal
Pro Has built-in Git support
Pro Nearly 100% of Rust code is interpretted by the IDE
The ability to trace variable definitions and references from within closures as well as understand smart pointers and macro code makes it the smoothest interface for writing Rust.
Pro Supports JS/TS frameworks
Cons
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 The autocomplete and code check is not as powerful as the one on WebStorm
Sometimes it doesn't tell you if you made a typo in a method name or if a method is not used and several other important features.
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 Project search limits results
Because file search is so slow your results are limited in order to simulate a faster search.
Con Very bad auto import
Con Generalized
VS Code is a general code/scripting IDE built to be lightweight and for people familiar with their language of choice, not directly comparable to Visual Studio in power or scope.
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 Poor error fix suggestions
Error detection and suggestions/fixes are poor compared to IntelliJ platforms
Con A "me too" offering from MS, far behind other well established editors that it attempts to clone
Other IDEs specific to a language often offer better tools for deep programming.
Con Slow launch time
Slower than it's competitors, e.g. Sublime Text.
Con Emmet plugin often fails on even simple p tags
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 .sass linting is terrible
Con Is not an IDE, is a text editor
Con Debugger requires paid CLion / IDEA Ultimate
Debugger still won't work without IDE that includes native debugger support. The only known is proprietary and paid CLion or IntelliJ IDEA Ultimate with the native debugger plugin.
Con Intellij Rust being replaced by paid for IDE
Con Why would you pay for it if there is VSCode
Con Too many issues (currently, in May 2022)
The plugin mostly works but it has a staggering number of issues (1400+ reported as of today). Therefore it should not be used if tool stability is an issue.
Con From the website: "work-in-progress, expect bugs and missing features"
Con Slow compared to Rust analyzer
Con Difficult to work with substrate
Con Does not parse macros correctly
It seems that autocomplete does not work for macros at all.