Migrated from #neovim back to #vim after several years of use because:
neovim-remote
is required. Vim has full local IPC workflow builtin.@jarkko I wish I could do the same. Only reason I switched to nvim was the LSP but now I have all the problems that you mentioned 😭
I guess it will be fine once I find time to actually wrap my head around it but migration from vim to nvim is definitely more than just a hot-swap 😕
@realestninja @jarkko Not a fan of LSP integration myself, but there are clients for Vim you could try:
- https://github.com/prabirshrestha/vim-lsp
- https://github.com/yegappan/lsp
The first one should be neovim-compatible as well, so you could try it out with your existing config.
@jarkko @realestninja Same, I'm very happy to rely on ctags. My issue with LSP is more about it *pushing* code changes to me, rather than being essentially a pull-based database.
For Rust, the usefulness is limited by how long it takes for rust-analyzer to start. With ctags, I can jump to identifiers immediately after opening a file, and if I rely on LSP, I have to wait for a looong time before it gets there.
My hot take is that LSP is such a crappy protocol it'll be dead in 5-10 years, but we'll see. Either way, I find it disappointing. It basically turns Vim into an IDE in the bad way: makes it as slow and clumsy as one.
As an example, here's me manipulating rust imports: https://www.youtube.com/watch?v=4yRGh0SGVok
If you wanted to do this via "code actions", you'd have to select what to do through some generic UI, and it only splits/merges two imports at a time. Kills all flow.