Hacker News debates whether Emacs and Vim can stay relevant in AI-driven development

Hacker News used Bozhidar Batsov's essay Emacs and Vim in the Age of AI as a proxy for a bigger argument: what exactly happens to programmable editors once coding shifts from typing to directing AI systems? The HN submission reached a score of 117 with 60 comments after it was posted on March 10, 2026. That made it one of the clearest community discussions this week about how developer tools are being re-ranked by AI, not simply extended by it.

Batsov's risk analysis is fairly direct. VS Code already has distribution and corporate backing, while Cursor, Windsurf, and other AI-first editors are being designed around agent loops, inline diffs, context management, and multi-file editing from day one. In that environment, the old promise of Emacs and Vim, making a human faster at the mechanical act of editing code, looks less decisive. If AI is producing most of the first draft, the bottleneck becomes specification quality, code review, and judgment. Batsov also argues that the funding gap matters: Microsoft and VC-backed startups can track new APIs and model capabilities full time, while Emacs, Vim, and Neovim communities mostly depend on volunteers.

But the essay is not a eulogy. Batsov's core counterpoint is that AI may lower one of the biggest historic barriers for both ecosystems: the difficulty of customization and plugin development. If users can describe desired behavior in plain English and get working Elisp, VimScript, or Lua, the extension-language barrier drops quickly. He also notes that AI integrations already exist, including gptel, ellama, aider.el, agent-shell, avante.nvim, and codecompanion.nvim. Terminal-native tools such as Claude Code and Aider may even fit classic editor workflows better than GUI-only AI products, because the agent and the editor can live in adjacent panes without forcing a full switch in environment.

The reason this mattered on HN is that it pushes the conversation past easy narratives like “legacy editors are dead” or “nothing changes.” The more convincing takeaway is that the editor is turning into a control surface for review, orchestration, and refinement. That shift could hurt ecosystems that depend on typing speed as their primary story, but it could also reward tools that are composable, inspectable, and deeply scriptable. For Emacs and Vim, survival may depend less on matching Cursor feature for feature and more on turning their existing flexibility into better AI workflows. The original essay is here: batsov.com/articles/2026/03/09/emacs-and-vim-in-the-age-of-ai.