Neovim's White Kight

Aidan writes...

I don't think Neovim gets enough love - I don't think vim would be making the changes it is today if Neovim hadn't come along (is it a coincidence that after years of nothing, vim 8 suddenly come out with async support shortly after Neovim started with async as a flagship feature). I started using and supporting Neovim when it launch in 2014, and have been following the nightly releases for most of that time. Writing this actually made me realize that that support has lapsed at some point (which I have rectified), so thank you for that.

Why Neovim? Cleaned up codebase, larger and more distributed development team (Bram is still a bottleneck afaik), and better defaults and abilities for modern systems (built in LSP and treesitter support, most recently).

Now that vimscript 9 is out, I would be interested in your take on rewriting the vimscript engine vs just using luajit, which is the direction Neovim took. I prefer the lua choice, as it is more widely applicable than vimscript and is going to have a wider development base (for the language itself).

- Aidan