Posts on the Neovim plugin ecosystem — modular plugin design, testing Lua inside the real editor in CI, and the distribution ecosystem that grew out of Yoda. Ships alongside the yoda-* plugin family: each piece independently useful, each piece independently testable.
A practical starter track: install Neovim, put your config in a GitHub repo you own, and layer on a small set of plugins that turn the empty editor into something you’ll want to keep using.
The case for Neovim from someone who spent thirty-plus years on vi and years on JetBrains before finally trying it — not because either was broken, but because Neovim’s customizability makes your editor a Personal Development Environment in a way IDEs can’t match. With concrete examples from the yoda.nvim distribution.
One Go binary that manages its own Neovim, runs Lua tests inside the real editor, and emits LCOV/Cobertura/JUnit — no system install, no vendored framework, no shell-script gymnastics.
yoda.nvim is a Neovim distribution built from a family of independently useful plugins — yoda-core, yoda-window, yoda-logging, yoda-diagnostics, yoda-terminal, and adapters. Modularity was the design goal, not a refactor after the fact.