Why Vim Felt Inevitable

Nikolai Shelekhov — Tue, 03 Feb 2026 00:00:00 +0000

I didn’t switch to Vim because it was trendy.
I switched because everything else started to feel wrong.</p>

It Started With Friction</h2>
Over time, I became increasingly sensitive to small inefficiencies:</p>

Reaching for the mouse</li>
Breaking typing flow</li>
Context switching between tools</li>
UI-heavy editors fighting my focus</li> </ul>
Individually, these are minor.
Collectively, they compound.</p>
As someone who cares about systems performance at the kernel and runtime level, it felt inconsistent to tolerate inefficiency in my own development workflow.</p>
The Ergonomics Shift</h2>
The turning point wasn’t Vim itself — it was ergonomics.</p>

Moving to compact keyboards</li>
Optimizing for home-row typing</li>
Reducing hand movement</li>
Eliminating unnecessary reach</li> </ul>
Once you train your hands to stay anchored, the mouse becomes an interruption.</p>
Traditional editors assume pointer interaction. Vim assumes intent expressed through motion.</p>
That difference is fundamental.</p>
Modal Editing and Systems Thinking</h2>
What clicked for me was this:</p>
Vim treats text editing like a language.</p>

Verbs (`d</code>, c</code>, y</code>)</li>`
`Motions (w</code>, }</code>, t(</code>)</li>`
Objects (iw</code>, ap</code>, etc.)</li> </ul> You compose actions instead of triggering commands.</p> That composability mirrors how I think about system design:</p> Small primitives</li> Clear contracts</li> Composable building blocks</li> Zero unnecessary abstraction</li> </ul> It felt closer to Rust than to an IDE.</p> Why Neovim (Not Just Vim)</h2> I eventually moved to Neovim for practical reasons:</p> Native LSP integration</li> Async plugin model</li> Lua configuration</li> Tight terminal integration</li> </ul> I wiped prebuilt configs and built my setup from scratch.</p> Not because prebuilt configs are bad — but because understanding your tools matters.</p> When your editor becomes infrastructure, you should know how it works.</p> The Real Benefit</h2> The biggest gain wasn’t speed.</p> It was flow.</p> Fewer context switches</li> No mouse dependency</li> Terminal + editor unified</li> Predictable behavior</li> </ul> The editor stopped being a UI and became an extension of intent.</p> Is It For Everyone?</h2> No.</p> Vim has a learning curve. It requires patience. It requires deliberate practice.</p> But if you:</p> Care about ergonomics</li> Think in composable primitives</li> Prefer keyboard-driven workflows</li> Enjoy understanding your tooling deeply</li> </ul> Then it may feel less like a choice — and more like inevitability.</p>