4 ms·
One of the big reasons is it has multithreading. So, you know when you have a plugin that's doing something and the whole editor locks up so you can't do anythi
by lojack 12y ago
One of the big reasons is it has multithreading. So, you know when you have a plugin that's doing something and the whole editor locks up so you can't do anything... with NeoVim there's a way to prevent that from occurring.
- sigzero 12y agoI tend to avoid plugins so that really has never happened to me. I can see how that would be annoying to those that do though.
- belak 12y agoAdditionally, neovim has gone through a huge code cleanup. Something vim will not do because they want to maintain infinite backwards compatibility. Many old builds have been dropped and a number of important things have started using libraries (libvterm just an example of this). In theory this won't change the functionality, but may, long term, improve stability. It's also nice that we aren't relying on one person to keep the project going. Bram is very dedicated, but when his response to "How can the community ensure that the Vim project succeeds for the foreseeable future?" is "Keep me alive", that doesn't say anything great about the project.
- comex 12y agobelak (author of dead sibling post to this one), FYI, you appear to be hellbanned.