2 ms·
Totally agree. I have been completely unable to learn vim beyond the basic commands and get it to stick and feel good as an editor, despite trying on and off, s
by barnabee 3y ago
Totally agree. I have been completely unable to learn vim beyond the basic commands and get it to stick and feel good as an editor, despite trying on and off, sometimes seriously, for two decades. Generally I think this is because of the unpredictability of actions, and the need to prepare them mentally ahead of time, with no visual feedback, then yolo the sequence of keypresses (and hope not to make a typo).
I didn't fully move away from editors like Sublime Text or VS Code when I discovered Kakoune, but I did finally find a modal editing model that makes sense to me. I work visually—the document I am working exists visually in my head, so I want that feedback (and I care about the latency in getting it).
Helix was the editor that got me to ditch all the others for a modal editor. The default keybindings are, in my view, even saner than Kakoune's. The visual feedback is better. And the fuzzy finder, space mode, LSP integration by default, etc. all make it a joy to work with pretty much out of the box.
I have no interest in spending hours/days/weeks/years on my config. I want to set a few preferences, pick a nice theme, and get to editing. Helix also delivers that better than any other editor I've tried. It's also rapid and uses next to no resources. It's not perfect, but it's developing fast and it's more usable for me than any other editor or IDE I've tried.
- orcy 3y agoI tried to re-learn from Vim to Helix but failed. No sure if this is a muscle memory problem or perhaps article is right about the cons Kakoune-like approach for me. Even adapting with something like https://github.com/LGUG2Z/helix-vim https://github.com/LGUG2Z/helix-vim did not work. So if you like Helix it probably a good thing that you did not learn the vim at the time.