[lordnaikon]

The ability to use plugins is no quality in itself. Even if Helix would support plugins tomorrow, it would not magically mean you could use the same (or equal) plugins from your vim experience – someone needs to write them. You can argue that the Helix Project is in its early stages but many of the features you get by crafting your vim config are running out of the box in Helix now.

There will very likely be a time when Plugins are supported, but this time is not now. I like the approach to make first class integrated functionality rather than the mess we currently have in vim. Helix aims to have an out of the box experience that would take you hours or even days if you are fresh to vim. If you need functionality on top of it, plugins will come into play. There is a reason why astrovim, spacevim etc. are popular, people don't want to spend to much time configuring the most basics that everyone is expecting today.

So if Helix does most of the things you need today i would encourage you to try it out and if it does not have a feature that you really need, plugins wouldn't help much either because somebody needs to write it in the first place and by the current userbase its very unlikely. It seems that most of the people are just gathering around the main project and make PR's directly which somewhat guarantees a certain amount of quality.

[efficax]

i agree that the plug-in chaos of vim and even emacs is exhausting. there’s so much churn, abandoned packages, and all this decision making that you have to do to get started. but at the same time you can’t expect to be able to build all the functionality into the editor. my workflow is greatly simplified by using tpopes vim-fugitive, it’s a fantastic git interface and it makes total sense to be part of an editor, and the lack of a similar thing in helix was the first reason i went back to vim after trying it out. if helix had plug-ins i’d probably be implementing that functionality myself! there are tons of other things like that. sure i could start building a git interface into helix itself but that both seems like a failure to separate concerns and a possible waste of time if it gets rejected by the maintainer etc.

[eviks]

> The ability to use plugins is no quality in itself

Theoretically no, practically, it is since someone is indeed more likely to extend the functionality via a plugin since the barrier is lower vs. adding the same thing to the core Also, for some things that someone could also be you

> Helix aims to have an out of the box experience that would take you hours or even days if you are fresh to vim.

Or you'd just copy the plugins/configs of someone who spend those days already, just like in those astro-space-packages you mentioned

[fileeditview]

As far as I remember they stated that plugins won't be supported back when I tried it. No idea if that has changed.

Of course the plugins need to be written but my point is that they cannot be written at the time.

I understand and support the idea of Helix to be useful out of the box for many use cases. However for me the editor in its current form is not sufficient. As I already stated I use many (wonderful) plugins in Neovim. I could not justify going away from the status quo because it is pretty good. I have my setup configured so the ease to jump into is not really a valid argument for me and I suspect for many more Vim users.

[lordnaikon]

I get what you're saying. The problem is that it is not really a matter of if plugins are supported or not. Helix will have plugins in the future. There is work being done towards it – mainly design work right now and they try to figure out how to approach this best, writing "demos" etc.

Plugin systems are not easy and they have a clear vision of how this should NOT end up working. In their current state putting in work into a Plugin-System does not make much sense (limited developer time that is better spend elsewhere) regarding their project goal.

As i said you can argue that the project is in its infancy and does not work for you because of that. But the main reason is not the support or lack of plugins. As i said, even if there was a plugin system you could argue that there are no plugins available for the things you want – ending up at exactly the same point you're today. Having a Plugin-System does not magically makes hundred of useful plugins appear out of nowhere.

[fileeditview]

I don't think you get my point. In the end it's simple. Helix misses many features I want and that exist in (N)Vim. To support all these features you need plugins because they cannot be all maintained by core and everyone wants different features anyways.

As long as there is no way to extend the editor for me or for anyone else (aside from contributing to core), I am not interested in adopting it when I have another option that already does all of these things I want.

So yes you need plugins but for that you first need a plugin system. If that takes a while I am totally fine with it. I am all for good software. But why should I currently choose it over nvim?

[SoraNoTenshi]

Helix will get plugin support sometime, it's basically a matter of when not if. Also; the scripting languages seems to become an S-Expression like lisp dialect.