3 ms·
> Am I alone in not jumping on the Visual Studio [Code] These are at least 3 different questions: 1) Why should I use VS Code in general? 2) Why should I use
by mbeex 5y ago
> Am I alone in not jumping on the Visual Studio [Code]
These are at least 3 different questions:
1) Why should I use VS Code in general?
2) Why should I use VS Code online? (the articles topic)
3) Why should I use VS?
The answers might turn out completely different.
Personally, I have for my main languages (C++ & Python) full IDE's (VS & Wing IDE). For quick Python scripts, VSCode is considered an option that I use rather often.
In what VSCode shines is - as also other commenters mentioned - his plugin eco-sytem. This has true swiss-knife traits. So I'm using it for many secondary and ad-hoc technologies:
- CMake files
- Julia
- GPS files
- JS files
- LaTeX
- JSON
- XML
- CSS
- Markdown (vanilla, asciidoc, ReST)
- remote editing
- SAI_Peregrinus 5y agoVS is unrelated to VS Code. VS is a full IDE for C++ and C# and the other .NET languages (and some other things like C to a lesser extent). VS Code is a decent text editor with a good plugin ecosystem. It's faster to start (if it doesn't have too many slow plugins) than most IDEs and easier to get used to than vi-based editors or EMACS. And unlike Sublime Text it's free. Unlike Notepad++ it's cross-platform. I personally use CLion for C (as well as Markdown, CMake, and shell scripts that are part of the same project as the C), PyCharm for Python, DataGrip for SQL, and VS Code for various text tasks like log file analysis and quick note taking. It's a handy editor, very useful for ad-hoc work but not really advantageous compared to a full IDE for most regular day-to-day work IMO.
- mbeex 5y agoYou should probably re-read the quote I was referring to.