DEV Community

Discussion on: VSCode vs Vim

Collapse
 
academicspade profile image
SpadeAcademic • Edited

My development work is fully in C++. My experience is thus: Began with Visual Studio IDE on Windows. Switched to VSCode since I had to develop the same code base on a Linux machine as well. Got swept up by the "VIM is faster/better than any other IDE" cult. Spent a few months using VIM as the IDE for C++. Then, got tired of polishing my .vimrc nonstop. Also was troubled that YCM autocomplete was very slow and buggy and lacking in features that VSCode and Visual Studio IDE have (for e.g., if you are filling the argument list of a function with large number of arguments, CtrlShiftSpace in VSCode/Visual Studio IDE tell you which parameter you are on. No such comparable feature in YCM). Vimspector debugging was not good enough (VSCode/Visual Studio provide logpoints capability, for instance) and there were tons of keyboard shortcut conflicts given all the plugins needed to turn VIM into a half-decent IDE. Gave up on VIM. I am now back to VSCode and Visual Studio IDE. They just work correctly and easily out of the box and have capabilities that are not available in VIM.

My advice for others reading this who are not yet committed to VIM -- do not get swept by the "VIM is smarter/better" madness. It is not. You are better of learning an actual IDE (any IDE would be fine) completely. You will be far more productive than you can every hope to be in VIM which is not an IDE nor was it ever meant to be one.

Visual Studio IDE also has the capability of integrating Intel VTune profiler which helps in finding hotstops in your algorithms much quicker. So, this IDE actually helps figure out how to make your code run faster. Of course this is possible in linux by running stuff through valgrind, etc. But that is outside of VIM. Visual Studio IDE is truly therefore an "Integrated" environment.