Vscode Vim VSCode vs Vim

VSCode (VSC) and VIM are my two main editors.

I sit within VSC almost all day every day. Editing on multiple devices gets annoying when switching over (Windows/macOS), but there are some plugins to help with that effort (search extension shan.code-settings-sync). VSC is a very powerful editor. Once you have keybinding setup, a few environment configs, and runners, you're good to go. The extension list is ever-expanding, and with that, you're more likely to find a few that really work well for you, or even make your own. Outside of the extensions, Intellisense is my saving grace. I often forget what functions are already implemented (or even the documentation and the argument variables) but that's when VSC is there holding my hand. The majority of work is in VSC because it's pretty on the eyes, integrated terminal for Windows (because no global hotkeys for iTerm2 like macOS) and the ability to work on various instances - even in the browser (see GitHub's new Codespaces?).

VIM is however my go-to editor. If I need things quick done now I run vim not vscode in my terminal to kick things off. Any time I'm remoting into a machine, I run vim. Even when VIM is not there, I install it, copy my dotfiles from GitHub, and continue with my day. VIM is excellent, fast to use - especially when you start understanding the basics - and there is still so much more I don't know about it and have to learn; but there's help with that (duh StackOverflow too). I recommend learning some of the basics in navigation for developers of any kind. Again, back to remoting into other machines, having an editor already there for you taking just a single config file and you're on your way is an amazing tool to have some skills with as a developer. It opens lots of doors, and just like the comments made here (by @wayofthepie) it's something that can take time doing, but once you get the basics, "[it's like playing an instrument...my fingers just know what to do.]"

Also, I know there are other terminal editors too, if one stands out then pick that one! Whatever makes you the most productive is the best for you and that's really all that matters. Stay safe 😄❤️

VSCode for development in local, vim for editing env files in production server.

They are both great. Used vscode mainly for about a year and really liked it. Didn't have to do much to get it working for most languages!

But I started getting some back, shoulder and wrist issues around that time. Not because of vscode, but because of how I sat and used my keyboard and mouse.

So I totally changed my whole workflow and setup. Moved to vim (well neovim) and switched to a tiling window manager so I could reduce mouse usage.

I spent a lot of time tweaking my vim setup to get what I wanted for the different languages and tooling I need to use. It's made me much more productive for sure. Not really faster overall - coding is mainly thinking 😄 - just more comfortable in translating those thoughts to code than I was with any other setup before.

It's become kind of like a musical instrument 🤔 I don't have to think much about performing a certain action, my fingers just know and do it.

Vim is amazingly powerful - but I can't be bothered to keep a map of key shortcuts in my brain.
VS Code - I might lose some time pointing and clicking, but it requires no extra mental arithmetic.

I can save that effort for creative problem solving. :)

I should add that I do have a level of envy for people who can do the former (including emacs users) - its impressive and I admire it. It's just one skill I've been unable to learn

Both VSCode and Vim are great editors with cult-like followings. Both have a great community built around them. For me it comes down to a few things that might not be of any importance to others. This is only my opinion and you're all welcome to take or leave it. First and foremost, I am not a Vim user nor will I ever be. I'm a strong advocate of pairing and Vim is painful to follow while pairing. I can't say the same for VSCode. If pairing is part of your team's workflow, Vim is a no go. In my experience VSCode just works and it doesn't require your pair to mind map to be efficient. I'll take the "slowdowns" that come with Electron apps in favor of all the built-in efficiencies for source control, debugging, and remote development. While the Vim community is large, it's ancient. Being a full stack engineer, I prefer my editor to stay as up to date as the technologies I'm using everyday. That's my two cents.

I always though of i as “inside” and a as “around”.