Re:I Still Use Vim
by GrantZvolsky on Thursday November 12, 2020 @04:30PM
(#25075347)
I share your experience, but it should only be a matter of time until the vim LSP clients[1] mature.
One notable exception is Go with its [vim-go](https://github.com/fatih/vim-go) plugin, which feels very mature to me as someone new to the language.
CoC is already there:
Re:I Still Use Vim
by blandflakes on Thursday November 12, 2020 @04:59PM
(#25075682)
Having to install node.js for a language server client is sort of a downer. For this reason I've been eagerly awaiting the built-in client in neovim, though it's definitely less polished and feature-complete than CoC today.
Isn't the "built in" neovim language server lua? I personally can't see much difference between having to install nodejs runtime Vs the lua runtime.
The difference is that the lua runtime is embedded (and wicked fast) into Neovim vs nodejs that has to go over the remote plugin interface
Fair enough. I've been using coc for a while now and can't say I've ever had any speed issues that I've noticed. But if the neocvm language server is built in and "as good" as CoC then that'll be one less plugin I'll need to install when it's ready.
Re:I Still Use Vim
by blandflakes on Thursday November 12, 2020 @05:46PM
(#25076271)
Yeah I don't have any node.js speed concerns for it, I just would like to have the simplest editor microservice architecture, and putting the client to a service in a service was a bridge further than I wanted.
Re:I Still Use Vim
by ogre_codes on Thursday November 12, 2020 @06:18PM
(#25076661)
CoC looks neat (installing right now), but it's a perfect example of what I mean. Having to poke through and add several dozen lines to my config file to get it working.
I would love to have this functionality with just
brew install ts-vim
And just be done with it.I don't use vscode that much, but when I was checking it out I installed some extension which lets you edit text with true neovim (point it to a bianry) while vscode handles chrome and code understanding. Worked pretty well.
Re:I Still Use Vim
by GrantZvolsky on Friday November 13, 2020 @03:45PM
(#25087255)
You're probably talking about Neo Vim[1] by Alexey Svetliakov. I can't recommend this one enough for a (neo)vim experience in VS Code. It is relatively new and deserves a lot more attention.
[1]: https://marketplace.visualstudio.com/items?itemName=asvetlia...
I use VIM for almost all basic editing. Its muscle memory.
But for code editing, I generally end up on VSCode because it seems to have better language support. I've spent a fair amount of time with configuring VIM trying to get where I feel it needs to be. But whenever I shift to a new stack, it always seems to take an investment of time and effort to get VIM set where it's better than VSCode.