I like rust-analyzer in VSCode, but I've found that it does seem to struggle with large projects that have multiple nested Cargo workspaces. IntelliJ with the Rust plugin has handled that (admittedly niche) case better so far. I still prefer VSCode though so I just open each workspace in an individual window and it works more or less as expected.
I gave up on JetBrains because most of their language plugins are broken most of the time. VSCode plugins have a much larger user base and tend to work, and I don't need 9 different products. It's similar to what happened to Atom.
The main downside of VSCode is Electron leaks memory like crazy and will use north of 150 GiB of RAM.
That's a crazy amount of memory usage, it might be an extension doing it? VSCode has a process explorer tool you can access under `Help>Open Process Explorer`.
I'm going to make a wild guess that you use macosx and that 150GiB isn't usage but addressed space. Macs are notorious for returning nonsense memory figures with some applications.
Incorrect and hairsplitting. It's a full IDE when you configure and use it properly. Meta uses a lightly-modified fork of it internally as their private IDE for internal use.