Live data from Hacker News

IntelliJ Rust

jetbrains.com

21–30 of 63 posts

Re: IntelliJ Rust

#21
post #2

When I used this plugin in CLion to work on Rust projects it felt very sluggish to me (I had to re-execute Cargo commands to get it to pick up on new files etc., and autocomplete basically didn't work). Has this been fixed, or was it some error on my end?

The plug-in itself is fine now, but linting through cargo check is frustratingly sluggish especially in repos with nontrivial Diesel codegen. Like noted in a sibling comment, it’s turned off by default and you get a notification suggesting you turn it off (uess you turn off the notification).

Re: IntelliJ Rust

#23

Serious question: why would I use this over VS Code + the Rust Analyzer extension?

Overall, I’ve found JetBrains IDEs to be “nicer” than VS Code. There’s a level of polish and thoughtfulness in the design that I’ve not found in VS Code. It’s hard to put into words, because it consists of lots of little things. Definitely not perfect though. Just better IMO.

Yeah agree. Jetbrains stuff just feels much more polished.

Re: IntelliJ Rust

#24
post #2

When I used this plugin in CLion to work on Rust projects it felt very sluggish to me (I had to re-execute Cargo commands to get it to pick up on new files etc., and autocomplete basically didn't work). Has this been fixed, or was it some error on my end?

What kind of system? IntelliJ has always seemed to require a lot of resources.

I bought 16GB a decade ago, for example, so I wouldn’t have swapping issues with my tools. That machine is still usable today.

Re: IntelliJ Rust

#25

Should Jetbrains make a specific Rust IDE? Would be cool!

I dont really get why Jetbrains even makes specific IDEs. I just use Intellij for everything and it seems to have same functionality as all their language specific IDEs?

Re: IntelliJ Rust

#26
post #3

Surely you mean "IntelliJ rs", right? Kidding aside, this is nice! Always happy to see more support for Rust, and I'm usually pretty impressed by what JetBrains brings to the table in their IDEs, so this is promising! Hopefully this will be one of those cases where the less you need an IDE, the more comfortable the features are for the ones that are built.

For anyone reading the comments with the assumption the OP link is just for the longstanding rust plugin, it is. Do not take the comment above to mean a standalone rust IDE, a la Goland, was announced. Hopes lifted, hopes dashed.

I'm pretty sure they're looking into creating an official one now. I recently received an email survey asking about using Rust and which IDE I use from JetBrains. I wouldn't be surprised if an official one comes out in the next year.

Re: IntelliJ Rust

#27
Last time I tried this, the plugin was incapable of actually showing compile errors in the project view and they said their false positive error rate was too high to enable it (https://github.com/intellij-rust/intellij-rust/pull/8373). That was a dealbreaker for me compared to VSCode. It doesn't look like that's changed?

Re: IntelliJ Rust

#28

Serious question: why would I use this over VS Code + the Rust Analyzer extension?

The plug-ins for JetBrains are often of a substantially better quality. Their database management extension is quite awesome. You get a lot out of the box too. Their support is usually very professional, if you ever need them. It runs on a JVM so you can tune it to your particular project requirements if you need but the defaults are fine. You shouldn’t turn on too many code inspections as they can slow down the UI responsiveness but you can tune the JVM and use a latency minimizing GC such as ZGC, though this is not something a regular user would ever need to look into I think. This will sound like an advert if I go on. And since I do a lot of other stuff in their IDEs, I have a uniform UI and UX.

Re: IntelliJ Rust

#30

Serious question: why would I use this over VS Code + the Rust Analyzer extension?

I've found that IntelliJ is much better at having code completion always work, even in the presence of macros. Rust Analyzer has a tendency to randomly break down when you're writing code, even with something as simple as the vec![] macro.

I reported one such case here: https://github.com/rust-lang/rust-analyzer/issues/12524, but this still happens to me pretty frequently.

Post reply on HN