this post was submitted on 03 Feb 2026
87 points (95.8% liked)
Open Source
44022 readers
468 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't understand the helix approach.
Let's build a new editor in rust (good), that is in the legacy of vim/nvim[/emacs] (good), that moves to resolve the backwards mechanics of the vim-syntax like meow (good) ... but let's build it all as built in features with no modularity ???
How can you build a new terminal editor like vim/nvim/emacs without realizing that the core strength is that the best features are delivered in plugins. Why would you try to write all of the functionality yourself? Why would you think that a small team can handle all of the work? How can you not realize that external contributors in vim/emacs are the source of the most interesting functionality?
I liked helix, almost as much as emacs w/ meow, but yiu xan't extend it, or write a plugin.
I suppose you can question the approach, but I personally can't argue against the results. I've been using it professionally and privately for almost two years and it rocks. I haven't had a need for plugins yet.