What's your editor?
Simple question. What do you use for editing Rust code? Why?
I'll start. I use VS Codium, but every now and then I give Neovim and even GNOME Builder a shot.
Syndicated from the fediverse. Read and engage on the original instance.
View original on kbin.socialView original on kbin.social
7 replies
I use Neovim, either with kickstarter.vim config or with astronvim.
I used VS Code, but it simply got to slow on my laptop of 12 years age. I therefore started to use helix and got hooked by the ideas of key bindings.
I then heard that Copilot X will / would work on neovim, and I might give it a try in the future I switched to neovim. Although still early I don't regret it at all. I finally understood why people are using it.
My biggest beef with Neovim is that because nothing is built-in, there are so many plugins required to make it feature-competitive with something like VS Codium. There are a million and one updates every single time I open Neovim. Lots of opportunities for something to break. I was using Lazy.nvim, but I am considering trying to do something simple from scratch and only add what I need. Configuration without these sort of Neovim distros is a bit weak though. Another fault I have with Neovim, especially since configurations can get insanely complex.
I am about to just try Vim keybindings in Codium, and see how that goes too.
VS code + rust code analyzer
I stick with it because I have settings and plugins for other languages that are required for my work
Neovim + lspconfig + rust-analyzer. I went to VSCode couple of months but came back in a day. Its so slowwwwwwwwwwwwww.....
Mostly helix. Love it. Not bloated, works well out of the box. Easy to configure. Quite well documented.