4 ms·
I like that Helix's approach is different, and I think the lack of plugins is essential for it to remain on its chosen path. If Helix got plugins, then soon eno
by dkarl 3y ago
I like that Helix's approach is different, and I think the lack of plugins is essential for it to remain on its chosen path. If Helix got plugins, then soon enough everybody would be scratching all their itches using plugins, there would be no users for the core functionality, and it would be the same kind of ecosystem we already have for emacs and Neovim.
What would be ideal for me, but probably not possible in reality, is an editor that cannibalizes popular plugins. So, if a feature is sorely lacking, the plugins appear, but eventually the core functionality grows to replace the plugins. A new user installs the editor and gets a rich set of features that are battle-tested and built to work together. What seems to happen in practice with emacs and Neovim is that the core never gets any bigger, so a new user gets zero benefit from those decades of work, experimentation, and discovery, until they invest the time to integrate dozens of disparate packages into their own setup which they will have to maintain themselves over time.
- eviks 3y agoBut that seems to happen in practice with emacs and vim, why would the newly designed editors follow the same rotten path, after all they've managed to break some significant conventions of those other editors? The other "in practice" side is that without plugins the editor will never get as good as a properly (though painfully, though less painfully with some preconfigured distribution) configured alternative one with plugins