If your Source Control Software is Team Foundation Server then skip Visual Studio Code. If you're using GitHub and are creating small projects Visual Studio Code is the way to go. If you need to create a large, enterprise-level application, Visual Studio Code makes it easier to set up interactions between related projects (client & server). If you're interested in getting back to the old way of using the command line to create projects and you know what to enter in the console window then Visual Studio Code is great. Visual Studio Code is a better choice if you don't know the console commands and prefer to make selections from a menu.
If you're doing any sort of text editing, you should consider Vim--once you climb the learning curve, you'll be faster and more efficient at everything you do. Also, Vim is my default search/replace tool--whenever I need to make changes throughout a document, most often, I'll copy and paste into a Vim window so that I can take advantage of regexp-based replacements. Vim isn't for the faint of heart, though--it's hard to learn and super complex. If you use a text editor once or twice a month, or just need a simple way to strip out formatting, Notepad will get you where you want to go without all the confusion.
Unlike for most languages I have used, Ruby and Rails support available for Code users isn't great. The most popular Ruby extension is unofficial, and leaves much to desire. As an example, code navigation even with language server Solargraph installed isn't as good as IntelliJ's RubyMine.
Even there is quite good support for a language or a framework, it is almost never as good as a dedicated IDE for it. In terms of the sheer number of features available, IntelliJ IDEs handily beat Code.
Microsoft has close-sourced some of the extensions it develops for Code itself, e.g. Pylance for Python, and that has not been perceived as a good move for open-source.
Solid tool that provides everything you need to develop most types of applications. The only reason not a 10 is that if you are doing large distributed teams on Enterprise level, Professional does provide more tools to support that and would be worth the cost.
Looking at our current implementation, Microsoft Visual Studio Code is perfect for writing code and performing debug operations. Integration with SVN repository is easy and changes can be tracked effectively. Microsoft Visual Studio Code supports developers to write code productively using syntax check and easy customization. Microsoft Visual Studio Code also provides support for IntelliSense which prompts suggestions for code completion. It is easy to step through code using interactive debugger to inspect the root cause of error quickly.
I don't consider the steep learning curve to be a hinderance on the overall usability. I would rate this a ten, but to be honest a lot of people do get hung up at the beginning and just abandon it. However, for people who have made the moderate effort to get over the hump, nothing can be more usable.
Active development means filing a bug on the GitHub repo typically gets you a response within 4 days. There are plugins for almost everything you need, whether it be linting, Vim emulation, even language servers (which I use to code in Scala). There is well-maintained official documentation. The only thing missing is forums. The closest thing is GitHub issues, which typically has the answers but is hard to sift through -- there are currently 78k issues.
The support is somewhat lacking; Vim doesn't really have support outside of its forums. The forums, while notably good, aren't equal to real support though, and the steep learning curve makes you wish there was a help desk that would assist with all of the basic questions. There are several handy books and guides that can be found, and most implementations of the product come with "vitutor" which walks you through its usage.
All the previously listed are incredible development environments that perfectly fulfill this function, but [Microsoft] Visual Studio Code goes one step ahead by providing flexibility, customization and adaptability to development environments with its own methodology, for all this productivity. of the work team is greatly increased helping to achieve the objectives set in the organization.
I think it comes down to usability (and frankly, just preference). There's an old adage that Emacs is a good Operating System with a poor Text Editor! Jokes aside, when looking at different text editors, such as Emacs or Nano, Vim is the one that is usually always preferred because of how simple it is to learn. The learning curve of Vim compared to other text editors just makes it such a natural choice.
