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.
I use VSCode with Vim keybindings. Mostly because it works without any problems, and I really like the inline-typing of the Rust Analyzer plugin.
I also use NeoVim on the side, but I am still faster in VSCode when I need to quickly jump between several files (at least until the day my vim-fu will improve).
Add comment