Helix: A post-modern text editor

Original Article ↗ Hacker News Discussion ↗

Overall sentiment

  • Many commenters use Helix as their primary terminal editor and praise it as “batteries‑included,” fast, and with tiny configs compared to Neovim/Vim.
  • Others like it for quick, server-side edits but still rely on VS Code, Neovim, or other IDEs for heavier work.
  • Several tried it, appreciated the ideas, but ultimately reverted to Vim/Neovim or Zed due to muscle memory and missing features.

Vim muscle memory & keybindings

  • A recurring theme: decades of Vim muscle memory make Helix’s different bindings painful to adopt.
  • Some report the transition took only days/weeks and are now happy; others find the differences (e.g., motions, selections, dd, G, {} vs ]p) too disruptive.
  • The “select-then-action” model and built‑in multi‑cursor behavior are seen as conceptually better by some but slower for frequent small edits.
  • Complaints about ergonomics: heavy use of Esc, extra ; to unselect, awkward keys for paragraph navigation, and inconsistencies (e.g., movement keys differing between editor and file explorer).

Features, plugins, and AI

  • LSP and Tree‑sitter “just working” out of the box is a major selling point.
  • Lack of a mature plugin system is a dealbreaker for some; people are watching a large plugin PR and upcoming releases closely.
  • Some feel Helix without plugins isn’t sufficient for “serious work,” despite LSP. Others see no issue for an “editor” role.
  • AI integration is currently mostly via LSP; several want deeper agent/AI tooling. Lack of live file reloads makes external AI tools awkward, though manual :reload/:reload-all exists.
  • Comparisons are drawn to ACP/MCP and various agent‑centric workflows, but there’s no consensus on the “right” integration model.

Performance, size, and implementation details

  • Users disagree on performance: many call it “snappy,” some say it can “chug” even on small files.
  • Binary sizes: reports range from ~20–30MB for the core binary to ~200MB of Tree‑sitter grammars, which compress very well.
  • Some criticize the large per‑language .so grammar files and Rust’s duplicated stdlib in plugins; others argue robust parsing beats regex grammars and disk is cheap, with filesystem compression as a workaround.

Missing / rough edges

  • Frequently mentioned gaps: code folding, virtual text (e.g., fold indicators, nicer markdown), better search/replace UX, easier multi‑line unselect, file explorer that can create/delete/rename, and automatic file-reload on external changes.