fix(editors.hbs): update recommended vscode extension

[jsjoeio]

It seems like based on this RFC, this Reddit thread, and some feedback I received on a YouTube video that the recommended extension to use is rust-analyzer.

I figured if that's the case, then shouldn't the official website reflect that? This PR updates the link.

[XAMPPRocky]

cc @matklad

[matklad]

cc @Xanewok

I think a fair summary of the current situation is:

• most people indeed find matklad.rust-analzyer to be better
• but it is not official extension yet, both in terms of community-wide decision that "yes, this is the thing", and in terms of proper release/security process
• we are merging matklad.rust-analyzer and the official extension into one, and most likely will finish this year.

So, I'd maybe keep this as is, for the time being. Or, (which needs significantly more work) would add a short explanation of "you can also try this one, it works better, but is not yet official".

[jsjoeio]

@matklad Do you have recommendations for content creators/teachers?

i.e. if I'm making a YouTube series about doing X with Rust in VS Code, which extension do I recommend?

[matklad]

@jsjoeio: I think it's important to mention all three of IntelliJ Rust, RLS, rust-analyzer. My personal recommendation is "try all and pick what works for you best".

[XAMPPRocky]

Okay, I'm going to close this as resolved for now. Thank you again for your PR!

[thomasaarholt]

@matklad is your former opinion still the case? I saw it mentioned on this reddit thread that people should be encouraged to use rust-analyzer over the current recommendation.
The Rust extension hasn't been updated in 10 months. Perhaps this PR should be reconsidered?

[matklad]

Yeah, I think #1242 (comment) is still true:

• it's clear that rust-analyzer overall provides significantly better experience than RLS, and that new users should generally be pointed to IntelliJ Rust or rust-analyzer
• at the same time, rust-analyzer is still not an official Rust project, and, as far as I understand this, this prevents us from actually recommending it as the official solution.
  • in addition to this org issue, there's a specific problem that rust-analyzer team manages rust-analyzer releases. While we do our best to ensure security, stability and all other "quality" thresholds, these probably needs to be transfert to proper release/dev tools teams.
• we are working on making rust-analyzer an official Rust project! It obviously didn't happen last year, it almost happened this year, hopefully it'll get done early next year.