For all those little papers scattered across your desk
It turns out I might have only written this down once, so here it is.
The short version is I use Vim
I find the (public, loud parts of the) Neovim community too willing to reimplement existing plugins or features just to say it was done in Lua2, too willing to hide complexity from novices in ways that make actually learning Vim’s roots hard (let alone debugging complex framework code)3, and a bit too “twitch gamer meme bro” for my personal tastes.
None of these things are bad; they don’t mesh with me.
In summary:
I continue to applaud their work to bring more people to the Vim ecosystem and turn more people into contributors. I wish that community was more willing to engage and collaborate with its sister, Vim.4
Lua seems more verbose to do the same thing when scripting editing tasks… Vim’s command language has a long history borne of editing powertools. Sure, its programmatic bits are odd, but you can learn those as you go and mostly by reading the manual (like any other tool). ↩
For just one example: why have dracula.nvim when dracula/vim has gone out of its way to be compatible with both editors? By all means, duplicate efforts… Or how about fugitive somehow having to “compete” with git-blame.nvim or blame.nvim? I’ve started a whole conversation at work to try to understand harpoon2 because it feels like “marks + Tbone + pick your favorite way to spawn terminals”—in other words, learn the builtins first? ↩
Looking at you, LazyVim. I know Vim pretty well, and it took me several hours to figure out what you did to make my brother-in-law’s Neovim open the Ex command line in a popup. Ugh. ↩
Christian Clason is the Neovim maintainer I most frequently see on the Vim mailing list, and I especially appreciate their efforts to stay in contact. ↩