Will Helix fall into config hell when plugin support comes out?

[Oneechan69]

I use Nvim rather than Helix, I've done some reading about it and I think its a pretty cool project; because it's not Vim and has nice features built-in. That's a good way to avoid a bunch of 3rd party plugin implementations.

I know some users switched from Emacs and Vim or Nvim, but right now a lot of users' Nvim workflows couldn't be recreated in Helix since a lot of functionality comes from plugins. I think a big advantage for Helix if most users could have feature-rich IDE setups without long configs and spending many hours working on them.

[kirawi]

No.

Helix will remain to be batteries-included.

[oxcrow]

Not likely.

If a new plugin is created in Steel and is well liked by most, then it should be included within Helix, by re-implementing the plugin's features using Rust.

Specifically because native compiled Rust will be faster than Steel, and that's one of the main advantages of Helix, which should always remain.

[deadb0d4]

Hey,

Thanks so much for your work on the editor. I've been enjoying it so much these days.
I never thought I would replace vscode for coding, but I have gone for helix for now.

As some people here and there, I am mildly concerned about the future of the editor
with regards to the introduction of the plugin system backed by Steel, but I understand
many reasons behind this decision.

I hope that the editor will only become better over time and will avoid becoming yet
another "weird" copy of vim or emacs, but otherwise, I am actually already content
with the current Jan. 2025 edition for the time being!

Don't take the above seriously ofc., and thanks so much for your work again.

All the best.

[Oneechan69]

Thanks so much for your work on the editor

I'm not a contributor to Helix just so u know