October 29, 2025
Key wars: clickers vs coders
From VS Code to Helix
Dev dumps VS Code for Helix; comments erupt: comfort vs keyboard cult
TLDR: A developer moved from VS Code to Helix over worries about AI creep and reliance on Big Tech. The comments split between convenience loyalists (VS Code, ubiquitous Vim) and values-driven keyboard fans, with retro jokes about ed and Stallman adding spice to a control-versus-comfort showdown.
A developer just swapped Microsoft’s mega-popular VS Code for the lean, keyboard-first Helix, citing unease with Big Tech and AI everywhere. He feared the complex, plugin-heavy world of Vim, but a simple tutorial and “just try it” mindset won him over. And then the internet did what it does best: argue, meme, and pick sides.
One loud camp shouted, “Vim is everywhere,” calling Helix nice but impractical when you can use Vim key shortcuts in almost any tool. The convenience crowd fired back: VS Code just works—drag-and-drop, remote features, and extensions in two clicks—who wants to memorize a hundred key combos? Meanwhile, the idealists rallied around the author’s trust-first stance, cheering the move away from Microsoft and dropping throwbacks like “ed is the standard editor” while debating historical baggage from the printer-and-teletype era. There were switcher confessions too: folks who forced themselves into Neovim and now swear it’s second nature.
The drama boils down to comfort vs control: click-friendly features and instant setup versus the keyboard cult promising speed, purity, and independence. Jokes flew (“two clicks vs fourteen keystrokes”), nostalgia surfaced (hello, Stallman), and the vibe was clear: editors aren’t just tools—they’re identity, workflow, and values.
Key Points
- •The author initially built their site using VS Code with Astro due to VS Code’s ease, extensions, and ubiquity.
- •Concerns about dependence on a single large vendor (Microsoft) and U.S.-based tooling motivated exploring alternatives.
- •The author prefers tools with sensible defaults over highly customized setups, which deterred them from vim/neovim.
- •After trialing Helix, it became comfortable within a week and the author’s primary editor within a few weeks.
- •A simple installation via “brew install helix” and Helix’s interactive official tutorial eased the transition.