Live data from Hacker News

Helix: A Neovim inspired editor, written in Rust

github.com

71–80 of 321 posts

Re: Helix: A Neovim inspired editor, written in Rust

#71
post #43
post #10

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…

> Helix is built from the ground up around Tree-Sitter and LSP And what happens in ten or twenty years, when both are obsolete? I don't really care, what technologies my text editor is built on top of, but I sure would like to be able to still use it for writing my memoirs when I'm old.

parsing is not a fad it has less chances of becoming obsolete, if any

Re: Helix: A Neovim inspired editor, written in Rust

#72
post #43
post #10

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…

> Helix is built from the ground up around Tree-Sitter and LSP And what happens in ten or twenty years, when both are obsolete? I don't really care, what technologies my text editor is built on top of, but I sure would like to be able to still use it for writing my memoirs when I'm old.

> And what happens in ten or twenty years, when both are obsolete?

I assume helix will be constantly evolving those ten or twenty years.

Re: Helix: A Neovim inspired editor, written in Rust

#73
post #58
post #55

Earlier quoted context omitted.

I like Helix, but it feels slow compared to Neovim. As in the actual scrolling performance. No one else has mentioned this, so I wonder if that’s an issue on my machine.

Might it be your terminal that too slow to render? You might want to try one of the many GPU accelerated terminals like Kitty, alacritty, wezterm, etc

I use alacritty. And I use Neovim on the same terminal.

Re: Helix: A Neovim inspired editor, written in Rust

#74

I have not tried the editor itself, but one thing that puts me off is how some people are claiming its going to replace vim/nevoim and others by the virtue of its great LSP and tree sitter support. I am working as a full time developer for the last 4-5 years and I never needed to use auto complete (for long words C-x n is there) and the current syntax highlighting seems fine. Vim is working great for me and I don't f…

No post body was provided.

Re: Helix: A Neovim inspired editor, written in Rust

#75
post #44

Earlier quoted context omitted.

I'd say that has been true in the past (and is still mostly true today), but I think this will change in the future. I have been using lsp+treesitter for markdown editing and it's been an excellent experience. It's still early days, but with treesitter and lsp being as universal as they are I've been seeing a lot of people just experimenting with what's possible. So yes, they are essential only for source code editin…

I'm looking forward to seeing Org Mode implemented as a language server. It's unfortunate that such a great general text organization tool is locked into the relatively small Emacs user community.

orgmode is so not a markup language and cant be served via lsp. its a whole ecosystem built on top of emacs. short of rewriting it, implementing it fully in another editor would require a sort of virtual emacs machine running in the background

Re: Helix: A Neovim inspired editor, written in Rust

#76

I have not tried the editor itself, but one thing that puts me off is how some people are claiming its going to replace vim/nevoim and others by the virtue of its great LSP and tree sitter support. I am working as a full time developer for the last 4-5 years and I never needed to use auto complete (for long words C-x n is there) and the current syntax highlighting seems fine. Vim is working great for me and I don't f…

Quoted post unavailable.

He very explicitly stated what about the post was off-putting to him. You made a comment about being personally attacked while repeating the tool is better without any argument whatsoever. You're exactly proving the point of the comment.

Re: Helix: A Neovim inspired editor, written in Rust

#77
post #76

Earlier quoted context omitted.

Quoted post unavailable.

He very explicitly stated what about the post was off-putting to him. You made a comment about being personally attacked while repeating the tool is better without any argument whatsoever. You're exactly proving the point of the comment.

No, they stated that they personally have no interest in using better tools (lsp, autocomplete etc).

Re: Helix: A Neovim inspired editor, written in Rust

#78
post #66
post #10

I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…

Can someone elaborate on why Vim doesn’t work well on non-english keyboards. I use Vim occasionally using a Nordic layout but would like to know why English is superior.

I'm a nordic-layout user as well and whenever I look at the actual differences side-by-side I get reminded about how much easier it would be to code if I had all those symbols that close.

https://www.farah.cl/Keyboardery/A-Visual-Comparison-of-Diff...

And for me I'm pretty sure that this "remap everything and translate every tutorial" barrier is why I never have been able to get into vim.

Re: Helix: A Neovim inspired editor, written in Rust

#80
post #76

Earlier quoted context omitted.

He very explicitly stated what about the post was off-putting to him. You made a comment about being personally attacked while repeating the tool is better without any argument whatsoever. You're exactly proving the point of the comment.

No, they stated that they personally have no interest in using better tools (lsp, autocomplete etc).

No, they contextualized that these improvements aren't actually improving anything for them, as they're not actually interested in using these features. And thus, it's no longer a better tool for them.
Post reply on HN