3 ms·
> let the package authors do the work of porting their packages. Unfortunately that will never happen, and since packages are the reason anyone uses anything,
by tines 6y ago
> let the package authors do the work of porting their packages.
Unfortunately that will never happen, and since packages are the reason anyone uses anything, no one will use the newmacs.
If there were a translation layer for backwards compatibility then that could work, but the one with more packages wins, so I don't think it could work without it.
- throwaway894345 6y agoNeovim is getting good traction in the vim space. It turns out that developers are also annoyed by these issues on legacy platforms and are motivated to support the new system.
- tines 6y agoI'm not familiar with the vim world. How different is the neovim API? Do the developers maintain two versions of their plugins?
- throwaway894345 6y agoI'm not that familiar with the details. My understanding is that neovim at least mostly supports the vim language, but also offers other APIs (not clear about whether these APIs are extensions of the VIM language or altogether different) that allow developers to work around common VIM issues. My crude impression is that developers actively prefer to interface with the new APIs, and many packages aren't even backwards compatible with VIM.