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.
Just regular VS Code. I didn't know about Codium! I think I'll switch over. I guess I can't add anything different but hope someone else shares their experience :)!
I've switched from vim to VSCodium some months ago.
In vim I was using Rust Language Server via vim-lsp. The editing experience was OK, and about half of the Rust code in my PassFish application was written using this setup.
At work we participated in a functional programming course hosted by FPComplete (their courses are awesome, btw), and during that course we used Visual Studio Code with Rust Analyzer, and that convinced me of the convenience of this setup. My personal setup is still a bit different, as I use VSCodium instead of Visual Studio Code, and instead of using the Rust-Analyzer binary that comes with the Visual Studio Code plugin I run the version that is (optionally) included in the Rust Gentoo package.
I've been using this setup for the second half of the Passfish development, and for the higher-free-macro crate I wrote. I'm mentioning that crate, because it has higher as a dependency, which in turn does some unholy type system magic, and is pushing Rust Analyzer to (and sometimes over) its limits. I'm pretty sure that Rust Language Server would have handled this crate better than Rust Analyzer, which quite often ended up freezing, and allocating gigabytes over gigabytes of RAM (only option: kill process....).
But still, I think VSCodium (or Visual Studio Code) together with Rust Analyzer is a pretty convenient IDE for Rust development, and it's definitely what I'd recommend for people starting out with the language.
Rustlang
Hot