Returning ~again~ to VIM
Visual Studio Code is a very powerful tool for writing code and I'm sure you'll be agree with me. An extensive number of plugins can help you in multiple ways; from connecting to local and remote databases, to coding in remote environments and forwarding ports on the fly of those remote apps. It's just magic!
What I like about Visual Studio Code...
VSCode allows me to connect to remote folders and work directly on them. Also, this IDE automatically detects what ports my application is listening and forwards them to my local machine; it feels like I'm working on my local machine all the time. Pretty cool!
Ok... but why returning to vim?
Easy to answer: “because
I'm crazy I like minimalism. To use VSCode I had to install and keep updated that software everytime; using VIM, I just to open a terminal and type
vim filename.ext and that's all! What about remote developement? Just connect via ssh to the server, code and so on. If i need to map some ports of my remote app I do it over ssh via ssh tunnels.
Finally, you choose tools depending on your needs.
VSCode or whatever IDE you choose and make you more productive is right; but if sometimes you don't want to overload your machine, try VIM and maybe you'll fall in love with this little text editor.
Cristhian Vega Cortes | Kernuac_CL