this post was submitted on 09 Feb 2025
112 points (99.1% liked)

Programming

18301 readers
105 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
112
Coders or lemmy, what editors do you use? Is it worth learning a new one? (self.programming)
submitted 1 week ago* (last edited 1 week ago) by verstra to c/programming
142 comments fedilink hide all child comments
 

When I was in high school I found Sublime Text and learned "multiple cursors". Since then, I've transitioned to vscode, mainly because I need LSP (without too much configuration work) for my work.

I keep hearing about how modal editing is faster and I would like to switch to a more performant editor. I've been looking at helix, as the 4th generation of the vi line of editors. Is anyone using it? Is it any good for the main code editor?

The problem that I have is that learning new editing keybindings would probably take me a month of time, before I get to the same amount of productivity (if I ever get here at all). So I'm looking for advice of people who have already done that before.

My code editing does involve a lot of "ctrl-arrow" to move around words, "ctrl-shift-arrow" to select words, "home/end" to move to beginning/end of the line, "ctrl-d" for "new cursor at next occurrence", "shift-alt-down" for "new cursor in the line below", "ctrl-shift-f" for "format file" and a few more to move around using LSP-provided "declaration"/"usages".

I would have to unlearn all of that.

Also, I do use "ctrl-arrow" to edit this post. Have you changed keybindings in firefox too?

you are viewing a single comment's thread
view the rest of the comments
[–] uthredii 25 points 1 week ago* (last edited 1 week ago) (6 children)

I use Helix

TLDR: Yes I think helix is worth trying out. It has some missing features but it is an amazing piece of software.

Yes I use helix daily. It is very fun to use and you can do many things faster. It is particularly good when navigating a (large) codebase you know fairly well. You are able to jump around and find/edit relevant code very quickly.

Compared to vs code:

  • it is much faster and more minimal
  • It might be harder to get things up and running than in vs code, e.g. to get auto-completion working in helix you need to have the LSP for that language installed. It can be a bit confusing if you have never done it before but it is easy once you have done it a few times.

Compared to neovim I think it is:

  • easier to learn
  • slightly faster - especially with large files
  • you will have a much smaller/simpler configuration. AFAIK Helix has more features working out of the box than neovim (file picker, lsp support ect) and needs less configuration to get things to a workable state.

The downside of helix compared to both neovim and vscode is that it does not have plugin support yet so you will need to use other tools in combination with it to get an equivalent experience. Here are some tools that are commonly used with helix:

Helix really shines when:

  • performance matters - I have edited files with millions of lines and had no trouble on codebases where my colleagues IDE's become very slow.
  • You want to use multiple cursors at times
  • You want a simple or no configuration
  • It is taking too long to learn the vim keybindings - vim keybindings are more concise but less intuitive and harder to learn

I recommend you use the tutor (hx --tutor) for a few minutes each day to learn the keybidings.

[–] verstra 9 points 1 week ago (1 children)

Thanks for the overview. I'll work with tutor and see how frustrated I get :D

Regarding language servers:

Recently, I got into this philosophy of "every project needs a declarative environment". It means that there is a committed file that should contain all tooling need to work with the project. Compilers, formatters, test runners and also: language servers.

This fights with vscode extensions which try to be clever and download their language server / bundle it into the extension itself. "No, rust-analyzer, I don't want your build because it does not work with xtensa target arch I'm using in this project".

So actually, this ties nicely with helix not providing the language servers itself, but allowing you to bring your own.

[–] uthredii 2 points 1 week ago

Yeah I agree, I like that aspect too!

load more comments (4 replies)