3 ms·

My problem is that some of that building should've been sensible defaults, and the community tends to outsource those responsibilities to extensions. Which mea

My problem is that some of that building should've been sensible defaults, and the community tends to outsource those responsibilities to extensions. Which means your Vim experience now has some risk of rot. Once and awhile my configurations/extensions rot and I have to go and update myself as to what happened in the ecosystem, or what is interacting with what. One day I decided I'm too tired and switched to VSC. Also the author failed to talk about the #1 killer feature of VSC, the reason for its meteoric rise in popularity — intellisense.

pkage 6y ago
Thankfully, you can get LSP-powered completion with coc.nvim, just like in VSC. It's miles better than YouCompleteMe, plus it's much easier to install—you can just use vim-plug or similar to install it. LSP is truly one of those "rising tide lifting all boats" projects. [0] https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim
- daotoad 6y ago
  I was using YCM and ALE to handle completion, but having switched to COC I won't look back. It's just a much better experience.
  - scruple 6y ago
    FWIW, neovim's built-in LSP (nvim-lspconfig -- written in Lua, currently in beta) is _outstanding_ and I have already replaced coc.nvim with it in my neovim set up. Set up is super simple, there are 2 extensions to install. Configuration is simple, I think I needed maybe 8 lines added to my `init.vim`. With that I get completion and in-line diagnostics and it's very, very fast, at least with solargraph, clangd, and tsserver.
ogre_codes 6y ago
> My problem is that some of that building should've been sensible defaults Vim suffers a bit from the design equivalent of tech debt. Much of the defaults and common behaviors were created based on the limits of software/ hardware 30+ years ago. Those limits still affect current design. > Also the author failed to talk about the #1 killer feature of VSC, the reason for its meteoric rise in popularity — intellisense. Given a fairly small amount of configuration, you can get autocomplete which is nearly as good as Intellisense in VSCode. For Typescript anyhow, the autocompletion comes from the same source background process.

pkage 6y ago

Thankfully, you can get LSP-powered completion with coc.nvim, just like in VSC. It's miles better than YouCompleteMe, plus it's much easier to install—you can just use vim-plug or similar to install it. LSP is truly one of those "rising tide lifting all boats" projects. [0] https://github.com/neoclide/coc.nvim https://github.com/neoclide/coc.nvim

daotoad 6y ago
I was using YCM and ALE to handle completion, but having switched to COC I won't look back. It's just a much better experience.
- scruple 6y ago
  FWIW, neovim's built-in LSP (nvim-lspconfig -- written in Lua, currently in beta) is _outstanding_ and I have already replaced coc.nvim with it in my neovim set up. Set up is super simple, there are 2 extensions to install. Configuration is simple, I think I needed maybe 8 lines added to my `init.vim`. With that I get completion and in-line diagnostics and it's very, very fast, at least with solargraph, clangd, and tsserver.

ogre_codes 6y ago

> My problem is that some of that building should've been sensible defaults Vim suffers a bit from the design equivalent of tech debt. Much of the defaults and common behaviors were created based on the limits of software/ hardware 30+ years ago. Those limits still affect current design. > Also the author failed to talk about the #1 killer feature of VSC, the reason for its meteoric rise in popularity — intellisense. Given a fairly small amount of configuration, you can get autocomplete which is nearly as good as Intellisense in VSCode. For Typescript anyhow, the autocompletion comes from the same source background process.