A Rustacean colleague kept singing Helix's praises. I discarded it because he's much smarter than I am, and I only ever use vim when I need to fiddle with files on a server. I like when things "Just Work" and didn't want to bother learning how to use Helix nor how to configure it.

Hacker News is a community-driven platform for sharing and discussing technology news, startups, and programming-related topics. Through user submissions and comments, Hacker News offers insights into emerging technology trends, industry developments, and entrepreneurial ventures. Readers can participate in discussions, share their insights, and stay informed about the latest advancements in technology and innovation.

Hacker News

A developer shares their journey switching from VS Code to Helix, a terminal-based text editor. Initially hesitant due to concerns about configuration complexity and learning curve, they were motivated by privacy concerns around Microsoft's AI integration and desire for open-source alternatives. The transition proved smoother than expected thanks to Helix's selection-first editing model and built-in tutorial. The post provides detailed setup instructions for Language Server Protocol integration with Markdown (using Marksman and Harper), Astro, and YAML, including formatters like dprint. While praising Helix's out-of-the-box philosophy and efficiency, the author notes the project struggles with PR backlog and could benefit from better contributor onboarding.

From VS Code to Helix

Getting the most of Markdown and Astro in Helix

Nice! Although, I wouldn’t drop Visual Studio Code entirely. I would use the right tool for the right job.

Nice article! I found out about rumdl and I’ll give it a try!

VS Code’s powerful UI and built-in terminal are great, but it’s getting heavy. Helix’s pure terminal setup feels faster and cleaner. At the end of the day, we use both based on our use case.