What does HackerNews think of helix?

A post-modern modal text editor.

Language: Rust

#55 in Rust
#4 in Vim
#14 in Vim
I've been test driving the Helix editor (mostly because of its out-of-the-box support for a wide range of LSP servers), and it adopts the kakoune style of keybindings. Like you, my muscle memory is very strongly in the Vim camp, and is hard to change :)

https://github.com/helix-editor/helix

this is basically why I moved to https://github.com/helix-editor/helix/ for most things. neovim setup is a nightmare these days. 0.5 introducing Lua was both great (yay! vimscript sucks!) and horrible (oh no, everyone took this power and made a full operating system worth of complex stuff out of it that rarely fits together cohesively, and it all updates so frequently now that I can't keep up)

I don't actually think it's Lua's fault. And I don't necessarily want to jump and say "the improved accessibility of this thing turned it into an unusable circus", because that's both unnecessarily sassy and also likely prescribing blame in some places it doesn't fully belong. But there's something that tidally changed in that time, and especially in the past 2-3 years, my vim setup became a thing I dreaded updating (because it would 100% guaranteed, every time, break something about my workflow)

This is exciting.

I've not had problems with latency in fish, but the promise of rust is that there is so little latency that it heralds a close to the metal feeling I've not seen in decades.

I think that feeling is visceral and laudable, regardless of the actual runtime profile. It's under-appreciated in the design community. IPC latency is as big a problem in operating systems and programming languages as RPC latency is in cloud systems.

I have no experience with rust, but I do depend on helix daily:

https://github.com/helix-editor/helix

and helix is rust.

I think this kind of open source experiment is exactly what we should be encouraging because it's forward-looking and straightforward to test.

I think the fish community could decide easily by A-B testing the Rust and C++ builds with real users and see how they compare in terms of reliability, performance, regressions, time-to-fix, and so on, assuming the team has the bandwidth to absorb the sideways nature of the work without derailing fish.

To me, rust is more than trendy and I can remember the first time I touched Walter Bright's work decades ago, so I'm open-minded about D too. A simple KLOC or cyclomatic complexity as a proxy to abstraction would be an interesting lens.

That "exhaustive" list doesn't include Helix[1], an editor with more than 400 contributors and 17k GitHub stars, which has been in development for close to three years, and which is probably more widely used already than 95% of the editors on that list ever were.

[1] https://github.com/helix-editor/helix

VSCode was my to-go for years but I had to force alternatives due to the increasingly bad practices I’ve seen by Microsoft. So I switched to vim. It has a large learning curve for me & the habits I have, and a lot or it requires work, but I have liked the change a lot — especially for remoting and working directly on other systems. It isn’t as convenient or easy, but the freedom is important.

Anyway, with regards to Rust, I was using https://github.com/helix-editor/helix for a bit as an editor. I ran into an issue with keymapping that was pretty basic but still an involved feature and so I set it down, but it is still very functional. A few years and it will be solid. And I agree with you, new offerings will come from Rust that will outcompete.