4 ms·
The promise is that given it's a new, modern codebase, it could quickly outpace vim in capabilities and usability. Vim's legacy is what is holding the editor ba
by cloudhead 10y ago
The promise is that given it's a new, modern codebase, it could quickly outpace vim in capabilities and usability. Vim's legacy is what is holding the editor back from major improvements.
- deleted 10y ago[deleted]
- Kurtz79 10y agoSo, the better question would be what advantages there are over Neovim :), but it has already been answered in another post.
- lolsal 10y agoIt sounds like you are saying it is better just because it is being written from scratch. I don't plan on contributing or writing any plugins to Vis (or vim) so I don't really care about what the 'guts' of the project look like as long as it does what I use it for (text editing). What motivation would I have to install Vis and deal with the mental overhead of switching (I am sincerely asking)? I have the same concerns with NeoVim. Maybe I just need to wait a decade for the ecosystem to catch up.
- cloudhead 10y agoYes. I would absolutely not advise to switch over at this point in time, unless you want to support the project. In its current state, I suspect it will be a poorer experience than vim and neovim.
- hyperbovine 10y agoWhat are the major improvements that cannot be added to Vim due to its legacy codebase? Honest question from a longtime vimmer.
- cloudhead 10y agoOne thing that comes to mind is that vim doesn't support multithreading very well or at all, when it comes to plugins. This is one of the issues Neovim is tackling.