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.

13m read timeFrom ergaster.org
Post cover image
Table of contents
Automation is a double-edged swordWhy I feared using HelixWhat HelpedGetting the most of Markdown and Astro in HelixIs it worth it?
5 Comments

Sort: