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 sensible defaults, 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 quickly thwarted by packer.nvim being deprecated right after I had gotten comfortably set up with it.

Well, coding has changed in the last year (to put it lightly). 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. Well, turns out the nvim ecosystem is a lot more stable, well-documented and network-effect-ified than it was in 2020. What’s more, you now have the option of vibe-configuring things to your liking in a half hour or less… Big news for people who hate configuring their editor.