The other factor that I think is even more underscoreable is that neovim doesn't really care.<p>Yes it integrates lua very well. But neovim is based around msgpack rpc! It's really easy to program/script neovim from <i>any</i> language, in a great defined way.<p>So there's like super easy to use Deno scripting too! That was ragingly cool for a bit, has calmed down, but so easy & straightforward to work with; truly a pleasure imo. <a href="https://github.com/vim-denops/denops.vim">https://github.com/vim-denops/denops.vim</a><p>The msgpack rpc just so easy to take whatever libraries you run into online & smash them into doing stuff in your neovim. Colossal epic super wins possible here!
As a counterexample, I'm super perplexed at the helix team -- an editor that myself and many others migrated to because we know / like rust -- decided on a lisp for their plugin system. Having recently tried to get into lisp (3 or 4 different highly recommended books / courses)... I really wish they had gone in a different direction here. Tempted to go back to nvim -- the lua config was pretty nice!
I remember trying Neovim in the early days because they kept talking about scripting with Lua. The problem I had was that I was new to the Vim/Neovim ecosystem and couldn't make head or tail of the documentation for using Lua. Maybe things are in a better state for someone like me.
As a long time vim users, elisp is something I always envied the emacs guys for. I love vim and bram but viml is a pos. The result were a multitude of language bindings. Of course, now everyone uses their favorite language to write extension which meant that most non trivial vim configs require a working python, perl, ruby and ocaml interpreter on the system. Lua in nvim fixes that, now I only need to install a billion language servers before I can start working :D
I just need ^W-j and ^W-k to work with terminal windows. Then I'll consider neovim. But I'm a pretty stock vim user, so there's not a lot of difference for me.