From VS Code to Helix
ergaster.org
From VS Code to Helix
1–10 of 142 posts
Re: From VS Code to Helix
#2Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via well-maintained plugins.
It's the same problem with keyboard layouts: I'm sure I could learn to be slightly faster on dvorak/colemak, but nothing beats the convenience of always having guaranteed access to qwerty, everywhere I go.
Re: From VS Code to Helix
#3Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
That keyboard layout is a great analogy. Maybe I would have tried Helix in my early twenties, but I’m too old for that now (30s lol).
Re: From VS Code to Helix
#4Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
This is what is keeping me from trying Helix in a serious way. I don't want to learn slightly distinct vi-like keybindings and mess up my muscle memory.
Re: From VS Code to Helix
#5Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
I have to agree. It is too similar to vim, yet it is not vim.... I dont get what is the value proposition here. I mean I feel helix is just stripped off SpaceVim ????
Re: From VS Code to Helix
#6Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
Eh. I've used a couple of different keyboard layouts and different keyboards and I can still use regular keyboards and layouts just fine.
It's just a matter of practice, which admittedly might be too much effort for little gain. I still use Neovim and I don't see myself ever using Helix or Kakoune.
Re: From VS Code to Helix
#7A few days ago I was randomly reading about ed (after stumbling with the 'ed is the standard editor' joke) and reflecting over how much historical baggage we accumulate in computing.
Commands like a for appending text are unchanged from the teletype era, which are so old that most people don't know computers used printers as an output before screens!
It's pushed me to learn about projects that try to move beyond acumulated baggage and rethink principles.
I've been taking a look at Nushell for example, and even though I was initially skeptical of Helix because of how universal vim commands are, perhaps it's time to take a deeper look.
Re: From VS Code to Helix
#8I have a similar story but with neovim (and for the same reason as the author; growing unease with big tech). Tried and failed to make the switch a few times but made a concerted effort to stick with it throughout a specific project and now it’s second nature. I found it useful to research idiomatic (n)vim ways of doing things whenever I’d get frustrated or feel I’d be doing something more quickly in VSCode and commit them to memory by using new commands a few times over. Right now I’d say search/replace is the only thing that’s still not as ergonomic for me in vim as it is in Code. What I do is visually highlight my search phrase, hit asterisk then :%s//replaced - I learned that you can omit the search pattern using this technique.
Anyway nvim and helix are both amazing and terminal editors are both cool and sexy, so why wouldn’t you? ;)
Re: From VS Code to Helix
#9Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
I have to agree. It is too similar to vim, yet it is not vim.... I dont get what is the value proposition here. I mean I feel helix is just stripped off SpaceVim ????
It's more intuitive, and some key binding are using home letters instead of symbols making it easier to reach
Re: From VS Code to Helix
#10I've tried Neovim, but still use VSCode because everything either works out of the box or takes 2 clicks to install an extension for and things like drag and drop into the file explorer or the remote extension make it really quick to use.
The only other real GUI contender I've seen is Jetbrains's IDEs (the free educational plan is great) but having seperate IDEs for different languages gets a bit annoying if you have multi language projects (e.g. a Rust backend hosting a Typescript frontend)