this post was submitted on 06 Nov 2025
175 points (94.4% liked)
Programming
23426 readers
124 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You probably already know this, but most IDEs have a setting to enable Vim keybinds or you can easily install an extension to add them.
I really like Neovim but my job often requires some stuff that it doesn’t easily do. So, VSCode is what I use a lot of the time… with the Vim extension.
Just something to consider if your stack isn’t super well supported in Vim/Neovim or you need tools it doesn’t have for your work.
I tried vim keybinds in an IDE, and it sucked.
It wasn't even that advanced usage, but it just didn't work.
Instead I know run language servers in neovim.
I agree with you. I figure you probably know this, but VS Code can act as a frontend for Neovim, providing one-to-one Neovim keybindings.
Some parts I never got working, but movement was honestly flawless. But I use a lot of snippets with ultisnips, and I didn't like the idea of translating all of that to hypersnips (or whatever the VS Code equivalent was called), so I stuck with Neovim.
Movement is like 20% of why vim is amazing.
Without macros I'm already out, registers are also mandatory, marks are very nice to have, etc.
I have trouble even remembering what are some of the features called, it's just musle memory now.