I switched after development ended on the package manager I was using on neovim. I didn’t at that moment want to simplify my vimconfig, so I looked into helix.

Helix highlights the action you take, so if for example, you are deleting 5 lines, you select the lines first then hit delete. Sometimes the vim actions end up taking fewer keystrokes though. And I still prefer some ways vim does things. And I don’t always agree with the kakoune inspiration of helix (I haven’t used kakoune, just going by what the docs say) - for example, movement always selects text which I then have to unhighlight.

But the biggest reason I stuck to helix was sane LSP defaults out of the box with minimal config. I was tired of having to fix LSP related bugs in my vim config after package updates.

TLDR: saner defaults for helix + lazy to fix my bloated vimconfig.

Immediately after you install helix, you can start working, no config required. It’s really nice.

It also has OOTB LSP, unlike in neovim where you have to setup manually for each installed LSP, helix just detects it. I also personally think it has better keybinds than neovim.

But it still doesn’t have a plugin system, and it’s quite opinionated. They’re both amazing, and great options. Just depends on what you want in an editor; customizability, or do you want it to just work.

i have sort of done this. the main thing is that the reversed object-verb command model just… latches onto your brain. this is from kakoune of course, but it just makes a lot of sense coming from vimland. multicursor I’ll also nice because it removes some modes, meaning there in less state to keep in your head. finally, the plug-and-play nature of helix meats you can have an lsp-enabled environment from the word go, with no configuration.

The neovim plugin for VSCode uses the actual nvim binary as a backend and supports all features.

https://xkcd.com/378/

Couldn’t help myself

That sounds tasty, where do I buy it?

To you, @toothpaste_ostrich@feddit.nl, and anyone else planning to do the switch:

Back when I was still a VSC(odium) user, you needed to perform a small tweak to regain access to the quite useful extensions marketplace (in the sense of, paste the extension ID, see the same results as a M$ VSCode user*): There is a file named product.json which allows you to “regain” access if you populate it with the following values:

{
  "extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "itemUrl": "https://marketplace.visualstudio.com/items",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "controlUrl": ""
  }
}

(Taken from my old dotfiles, so this may be outdated, not sure. Also, you’ll have to look up the location of this file, it will differ depending on OS. On macOS it goes in ~/Library/Application Support/VSCodium.)

*If you do not need this 1:1 identical functionality, you may try the Open VSX marketplace. But especially in a class setting, I found this very useful, since all the tutorials/instructions will work without needing adaptation.

Exactly! It’s rare to find such old things that are still excellent today

You can do that with vscode too. And probably many IDEs.

The only real reason for which you would need to use vim in such cases is if the target computer can’t run the vscode server, which I’ve never encountered yet.

Tramp is more featured, but if all one cares about is being able to edit remote files using a local editor, vim can edit remote files with scp too: scp://user@server[:port]//remote/file.txt

I tried tramp-mode at some point, but I seem to remember some gotchas with LSP and pretty bleh latency, which didn’t make it all that useful to me… But I admittedly didn’t spend much time in emacs land.