But I don't do things like jumping to declarations with it. That's likely a thing with some plugin, I just don't know. I generally try to avoid traditional OO languages when I can. I used to use IntelliJ for those, but I have actually switched to VSCode for them and some of the things I've always used vim/neovim for, like larger Go projects.
I make any IDE act like vim because my hands want to do modal editing. That's a thing where my habits impact my perceived ergonomics. If it doesn't support that, I won't use it. It's just too frustrating.
I don't use Javascript except when I have to. If that's part of a TUI VSCode for you, then this may not be helpful.
Nothing could be further from the truth. There are tons of plugins, scripts, tutorials for literally every scenario you can imagine since Vim has (never mind its predecessor Vi) has been around since 1991.
at some point you just can't do everything with single letters, you need actual, complex commands
Vim’s power is its composability. Once you understand text objects (word, sentences, paragraphs) and motions, you can do anything you want.
If you need to repeat a string of commands together, you can record macros on the fly, create an autocommand or a plugin if that’s what needed.
Neovim in particular has LSP support built-in, which gives the editor semantic knowledge of your code, just like an IDE. So renaming, refactoring, formatting, syntax highlighting work better.
There’s even a LSP server for Free Pascal:https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser....