12 ms·

To my knowledge, maintaining compatibility is one of the stated goals of Vim, even at the expense of performance. NeoVim is supposed to strip out some of these

To my knowledge, maintaining compatibility is one of the stated goals of Vim, even at the expense of performance. NeoVim is supposed to strip out some of these antiquated features.

wyldfire 11y ago
But the ifdefs likely negate performance concerns for the most part. Decomposing this function into different implementations with appropriate abstraction doesn't need to break compatibility.
austinl 11y ago
Also, it just so happens that the people working on NeoVim are currently porting all IO to libuv (the cross-platform library mentioned in the article). https://github.com/neovim/neovim#whats-being-worked-on-now https://github.com/neovim/neovim#whats-being-worked-on-now
- chronial 11y ago
  See here: https://github.com/neovim/neovim/commit/4528046 https://github.com/neovim/neovim/commit/4528046
carterehsmith 11y ago
It is a good goal for sure. That said, how does one go about submitting a "fix" for such a widely deployed software? Like, before submitting, I need to make sure it works on Amiga, VMS, Irix... and then all the current platforms. That is, like, a pretty high barrier... who in the world has all these platforms handy for testing? You submit a patch and someone says that it has a problem on Xenix 2.37.4 -- what do you do?
- ForHackernews 11y ago
  > who in the world has all these platforms handy for testing? This was the OpenBSD project's testing rack in 2009: http://www.openbsd.org/images/rack2009.jpg http://www.openbsd.org/images/rack2009.jpg