4 ms·

I believe neovim started as a fork specifically to implement features like LSP support and package management, VIM eventually also caught up. But i don't believ

I believe neovim started as a fork specifically to implement features like LSP support and package management, VIM eventually also caught up. But i don't believe anything is out of the table, or against Vim tradition. Which features do you want to see built-in, specifically?

QuantumNomad_ 7mo ago
I’m also pretty sure that on an episode of The Standup, one of the Neovim core maintainers TJ DeVries (Teej) said that it is a good idea to prove new ideas in the form of a plugin rather than submitting pull requests for Neovim itself with new ideas that have not yet been tested out and proven in the real world. Implicitly implying that indeed Neovim is open to bring features from plugins into core Neovim itself, if they are proven to be useful for a lot of people. Unfortunately I don’t remember what episode it was or even if it was specifically on an episode of The Standup, or if it was some other video that he and ThePrimagen did outside of The Standup.
- GCUMstlyHarmls 7mo ago
  This is essentially how the new package manager got done. `mini.deps` was created as basically a proposal for a built in package manager (beyond also just being its own thing), sat in the wild for a year or two then a derived version got imported.
aidos 7mo ago
Multi threading, but yeah. Original HN post here if you’re interested. https://news.ycombinator.com/item?id=7279358 https://news.ycombinator.com/item?id=7279358
- mi_lk 7mo ago
  > The author of NeoVim (Thiago de Arruda) I've always wondered what this legend is doing now