Well, we're almost forced to use printing because of the current state of the debugger in RustRover (or the Rust plugin, that will probably be abandoned). VSCode isn't a real IDE but it's free and it makes a much better job at it. For ex, when displaying values in a native, rust-fmt way or when showing variables that are already known at the breakpoint. Since those problems, like many others, have been around for months or even years, I'm concerned JetBrains is more invested in developing new features to attract more customers than spending time on stabilizing them. But hey, now we have AI tools, right.
I've found the same when I tried it a few months ago. I've been wanting to try it again, but I don't really expect it to be as polished as other jetbrains ides yet.
@@kevinmcfarlane2752 It's as stable as their other IDEs and plugins (which isn't to say it's 100% stable if you know them), and more like an advanced beta stage, I'd say. The debugger is unusable in a number of cases, but the IDE has all the features you need to develop projects, as much as other languages like Java and Kotlin. It's definitely more comfortable than using VSCode for me, but I know it's subjective. The code awareness is good, it makes useful completion suggestions, it can show the expanded macros (which is a great help given how they're abused in Rust), perform reliable factorization, launch most tests with a click, ... Actually, the platform is fine. It's the plugin itself that is being worked on, and if you checked it when it was still open source, you must have seen it had an impressive number of issues. Still, it's quite OK; I just wish they were fixing the issues rather than adding even more stuff on a base that isn't fully stable.
Well, we're almost forced to use printing because of the current state of the debugger in RustRover (or the Rust plugin, that will probably be abandoned). VSCode isn't a real IDE but it's free and it makes a much better job at it. For ex, when displaying values in a native, rust-fmt way or when showing variables that are already known at the breakpoint. Since those problems, like many others, have been around for months or even years, I'm concerned JetBrains is more invested in developing new features to attract more customers than spending time on stabilizing them. But hey, now we have AI tools, right.
I've been using RustRover and it is not really stable. Lots of errors and faults.
What is its current status? Alpha? Beta?
I've found the same when I tried it a few months ago. I've been wanting to try it again, but I don't really expect it to be as polished as other jetbrains ides yet.
@@kevinmcfarlane2752 It's as stable as their other IDEs and plugins (which isn't to say it's 100% stable if you know them), and more like an advanced beta stage, I'd say. The debugger is unusable in a number of cases, but the IDE has all the features you need to develop projects, as much as other languages like Java and Kotlin. It's definitely more comfortable than using VSCode for me, but I know it's subjective. The code awareness is good, it makes useful completion suggestions, it can show the expanded macros (which is a great help given how they're abused in Rust), perform reliable factorization, launch most tests with a click, ... Actually, the platform is fine. It's the plugin itself that is being worked on, and if you checked it when it was still open source, you must have seen it had an impressive number of issues. Still, it's quite OK; I just wish they were fixing the issues rather than adding even more stuff on a base that isn't fully stable.