Neovim

bikeshedding story arc

Back in high school, I ditched Vim/Neovim as an editor in favor of VSCode/Codium with this lovely extension because I couldn’t be bothered to configure anything beyond a handful of keybindings, liked VSC’s broader out-of-the-box feature set, and preferred clicking buttons to writing configuration files. Neovim’s config/plugin ecosystem was still fragmented and warty at the time. (any uncs remember Vim Script??) LSP was still newish back then and support for it outside of vscode was a little spotty too.

Mid-hiatus, my one attempt to try neovim again was hindered by having to dig around in plugin docs to turn on the aforementioned expected OOTB features, and was finally done in when I was in the middle of setting up packer.nvim and found out from a friend that it was being deprecated.

Anyway, coding has changed in the last year (to put it lightly), and as a result of living in the terminal with Codex/OpenCode, I recently stopped using an IDE altogether and started using Neovim again for what remaining pointed edits are required of me. Doing this, I found that Neovim’s ecosystem is a lot more stable & network-effect-ified than it was in 2020. What’s more, you now have the option of vibe-customizing things to your liking in a half hour or less. Big news for people who hate configuring their editor and are OK with agents running roughshod over their home directories.

Thanks, LLMs. Neovim now works amazingly for me, and I barely use it.