It's not that cut and dry.
See https://github.com/onivim/libvim#why-is-libvim-based-on-vim-...
It's mostly due to their build system.
See https://github.com/onivim/libvim#why-is-libvim-based-on-vim-...
It's mostly due to their build system.
> 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.