5 ms·
Technically, Neovim started because the author wanted to add multi-threading to Vim but the patch was rejected. So they did try to contribuir to Vim first. Not
by latexr 9mo ago
Technically, Neovim started because the author wanted to add multi-threading to Vim but the patch was rejected. So they did try to contribuir to Vim first.
Not that I agree with your parent comment or anything (I don’t), I use Helix so don’t really have a dog in this fight, I think it’s fine for them all to coexist.
- aniviacat 9mo agoDo you know why it was rejected?
- worldsavior 9mo agohttps://news.ycombinator.com/item?id=7279358 https://news.ycombinator.com/item?id=7279358
- mos87 9mo agoSome good context...
- latexr 9mo agoIt’s been too long, I no longer recall specifics. Wikipedia links to the patch’s discussion on Google Groups, if you care to read it. https://groups.google.com/g/vim_dev/c/65jjGqS1_VQ/m/fFiFrrIBwNAJ https://groups.google.com/g/vim_dev/c/65jjGqS1_VQ/m/fFiFrrIB... Vim 8 did add support for asynchronous jobs, due to the pressure of Neovim fork. https://lwn.net/Articles/713114/ https://lwn.net/Articles/713114/
- mos87 9mo agoAnd did so in its (or rather Bram's) own, incompatible with Neovim way. I imagine that's the biggest problem with Vim why Neovim was even created - hardcore NIH syndrome of Vim's main author.