| ▲ | evanjrowley a day ago | |||||||
Commenting as an outsider to both projects, one possible motivation to fork Helix might be this PR: https://github.com/helix-editor/helix/pull/8675 Helix was originally meant to be a "batteries included" editor without any scripting/plugins. That PR intends to change this and so there is a bit of controversy around it. Overall it looks like the PR will eventually be merged. The Mitos fork could have be made for totally unrelated reasons. This is really just my speculation. | ||||||||
| ▲ | riedel a day ago | parent | next [-] | |||||||
From the commit history it rather looks like an ai agent speed run of a single guy frustrated about this not moving fast enough. | ||||||||
| ▲ | __m a day ago | parent | prev | next [-] | |||||||
The most recent activity in that PR comes from mitos. | ||||||||
| ▲ | notnmeyer a day ago | parent | prev | next [-] | |||||||
helix has a plugin system in the works, but unsure when it’ll actually land. lots of folks are already daily driving it, myself included. | ||||||||
| ▲ | srott a day ago | parent | prev | next [-] | |||||||
Treesitter grammar for each language does not count as plugin? I think I had seen some dynamic libs when I tried to build it… | ||||||||
| ▲ | satvikpendem 18 hours ago | parent | prev [-] | |||||||
I commented on that PR a few years ago and got downvoted, primarily for asking why they're using some random person's pet Lisp-in-Rust project over something more established, even Lua like Neovim is. I still don't understand why, but in the age of AI looks like we can build anything we want instead. | ||||||||
| ||||||||