Helix: A post-modern text editor
doener
32 points
6 comments
March 06, 2026
Related Discussions
Found 5 related stories in 78.1ms across 3,471 title embeddings via pgvector HNSW
- Show HN: Revise – An AI Editor for Documents artursapek · 64 pts · March 22, 2026 · 58% similar
- Show HN: Free, in-browser PDF editor philjohnson · 51 pts · March 28, 2026 · 56% similar
- Writing my own text editor, and daily-driving it todsacerdoti · 56 pts · March 11, 2026 · 55% similar
- The future of text layout is not CSS skeptrune · 12 pts · March 28, 2026 · 52% similar
- Show HN: Mesa – A collaborative canvas IDE built for agent-first development visekr · 15 pts · March 13, 2026 · 51% similar
Discussion Highlights (3 comments)
canistel
Do have a look at the second question in the FAQ :). I do find Helix very impressive. I remember the Python LSP working without any configuration whatsoever. However, I have vim muscle memory built over 25 years of use. I already struggle switching between Emacs and vim (or its equivalents) - for example, after a period of vim usage, I would press ESC repeatedly in Emacs, three of which are enough close a window. While Helix borrows modal editing from vim, it introduces subtle (and meaningful - I have to admit) variations, which unfortunately wreaks havoc with my muscle memory. Maybe the worst part about muscle memory is that unlearning is almost impossible. My dilemma, not Helix's fault...
Panzerschrek
I tried using it once by compiling it from sources. Even a release build is several hundred megabytes in size, which I find pretty wasteful. After a little investigation I found, that it has many plugins in form of a shared library, and each of them has pretty huge size, presumably because the whole Rust standard library is statically linked.
dalanmiller
Love `hx`, vim never really clicked for me and the batteries-included nature of helix is one of its best selling points.