3 ms·

It's not that cut and dry. See https://github.com/onivim/libvim#why-is-libvim-based-on-vim-and-not-neovim https://github.com/onivim/libvim#why-is-libvim-based-

by nhooyr 6y ago

It's not that cut and dry. See https://github.com/onivim/libvim#why-is-libvim-based-on-vim-and-not-neovim https://github.com/onivim/libvim#why-is-libvim-based-on-vim-... It's mostly due to their build system.

gw 6y ago
I've seen that but Bryan said this just a few days ago: > This was a smaller consideration - but more fundamentally, the model Neovim uses for input - queuing it on an event loop and handling it asynchronously - is at odds with what we required - to be able to process the input -> handle updates synchronously. https://news.ycombinator.com/item?id=23628381 https://news.ycombinator.com/item?id=23628381