Really like the sane defaults with Helix, just waiting like many users for the copilot integration. (https://github.com/helix-editor/helix/issues/1927)
Helix: A Neovim inspired editor, written in Rust
81–90 of 321 posts
Re: Helix: A Neovim inspired editor, written in Rust
#82Earlier 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).
He is saying that these tools aren't improving his dev process and therefore are not better for him.
Better is also such a subjective feeling - please either quantify the improvement or don't present it as an objective truth.
Re: Helix: A Neovim inspired editor, written in Rust
#83I 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…
> by the virtue of its great LSP and tree sitter support.
> maybe just tell ... why people would want to use it?
Apparently they did tell you, and you’re not interested. Fine, but what a pointless comment. Rob Pike will also tell you how he loves coding without syntax highlighting, which you apparently find useful.
Re: Helix: A Neovim inspired editor, written in Rust
#84Earlier quoted context omitted.
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.
I grew up with the Icelandic layout. When I started programming professionally I taught myself the en-us layout and stared using that instead. It is much easier on my hands and fingers; it really does show that the people who came up with the syntax for most of the programming languages in use picked things that were easy to type on a US layout and didn't give any thought to the rest of us.
Re: Helix: A Neovim inspired editor, written in Rust
#85Played around with a bit. In my experience compared to a configured vim:
- once you have your local language servers available it works quite nicely out of the box. syntax highlighting, file finder, lsp navigation, formatting, etc. just works
- its fast
- i really like having the order of selection->action instead of action->movement
- im still missing some features like a navigation tree and a quickfix list or something to do project wide find/replace.
Re: Helix: A Neovim inspired editor, written in Rust
#86I 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…
I just can't see if ever taking off, if I'm honest. The people that use neo/vim are going to continue using it, even if Helix is better. The people who aren't yet using it will use vs-code and the few that do switch, well they might go to Helix but there's a lot of vim resources out there, so I'm not sure all of them will go to Helix. Honestly, language servers are a bit of a faff to set up, but that's tooling and it…
> I just can't see if ever taking off, if I'm honest. The people that use neo/vim are going to continue using it, even if Helix is better.
I would think that helix probably is better because I'm certain that the verb->text object paradigm in vim could be much better. It may in fact make more sense to do the 'text object' first like it seems to do in both helix and kakoune. But is it better enough for me to switch off something that I've used for years now? Only if it sees mass adoption and you see many developers adopting it. Like if you see it in VS Code as an option to use helix bindings, then it is probably safe to consider adopting it.
> Honestly, language servers are a bit of a faff to set up, but that's tooling and it's getting easier and easier to get these installed now. I expect that will continue.
I've been pleasantly surprised with how much better LSP setup in neovim has gotten, as I've transitioned over to the native LSP from CoC, which is also excellent. It's still not pain-free to setup, but it's much easier than it was and I suspect you're right that it'll continue to get easier... though I doubt it'll get anywhere close to how easy VS Code is to use any time soon.
Re: Helix: A Neovim inspired editor, written in Rust
#87I 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…
When you say you never needed LSP, do you mean you've tried it and found no benefit to having it, or do you mean you're doing just fine without it? (Because its possible to do just fine without it yet still find significant benefit to having it).
What LSP does for me is instant documentation integrated into the editor and getting constant feedback if you get it wrong (at least from a typechecking perspective). I guess that in many cases, you can get something similar by having a documentation window open on the side as well as automated unit tests in a second terminal re-running on every save.
Re: Helix: A Neovim inspired editor, written in Rust
#88I'm a Kakoune user. What will change in my life if I move to Helix?
Re: Helix: A Neovim inspired editor, written in Rust
#89I 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.
Here's some advice from a Norwegian who programmed in Vim for years on the nordic layout: do yourself a favor and get an American keyboard ASAP. The brackets alone are worth it.
Re: Helix: A Neovim inspired editor, written in Rust
#90I 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…
> Those are by far the most important features for a text editor to have
The most important feature of an IDE is to be easy to use, having powerful functionalities is important too, but that's goes after.. VSCode has nailed the first point. Wake me up when (neo)vim/kakoune/Helix has a "list of tab view" similar to VSCode..