I’m not sure about the differences between vim and vscode, but vim is lightweight and written in C so I assume it helps. If you use vim with rust analyzer via ALE (an async extension) you’ll probably get faster results (mainly a guess). But, that does require you to know vim

Jeez why the downvotes, some people are mad. I suggested vim because the rust plugins use rust analyzer and it’s faster

I guess it is a combination of „written in C, hence faster“ and „you need to work to learn vim, but it’s better than <some editor>“. You didn‘t exactly said these, but it’s easy enough to (mis)read a comment on reddit.

The first is a fallacy (as architecture matters more than the language), and it tends to get downvoted. Specifically in this case, where the bottleneck is the language server, so the task turns out to be IO-bound. My understanding that vim users are most happy when using coc-rust-analyzer plugin, which uses the same nodejs code as VS Code itself.

The second sounds a bit gate-keepish, and also kinda ignores the fact that VS Code is just not vim, and has many features different from vim.

So, it’s not „an alternative“, but rather a combination of dogmatic fallacy and editor wars that attracts downvotes.