I really like developing Rust with CLion: when I'm using C libs and Rust bindings, I can debug it seamlessly and efficiently. If RustRover [1], the dedicated JetBrains IDE for Rust, doesn't support C/C++, It will be a showstopper for switching.
Now I'm working on a Rust + CUDA FFI project; RustRover has minimal support for the CUDA (essentially C++) code. It does syntax highlighting and comment-hotkey, but the introspection and refactoring appear inop. It would be nice if RustRover and CLion were combined.
Just switch to Clion and You'll problem will be solved
Multi-language code bases aren't that uncommon either. As you say mixing C and Rust is common in apps and systems level programming. Mixing JavaScript, TypeScript, Go, and other languages like Python is also pretty common in web-centric stuff.
Whereas you get the whole experience on Eclipse out of the box.
To keep in context, to this day you can't debug JNI on regular InteliJ, unless having CLion as well.
Something that Netbeans and Eclipse support for at least 20 years now.
(It still exists but seems kind of dead outside Java shops.)
The plugin ecosystem from VSCode is the only reason I tolerate an Electron powered editor for specific use cases.
These days I only do Rust dev really. I'm not clear on what their plans are for ongoing Rust support in CLion going forward now that they're rolling out RustRover. Are they going to pull it?!
Because I work at a company that is mostly C++, with some Rust. My team's project is 90% Rust, but I still need to do C++ now and then. I'd be super annoyed to lose that.
They should at least continue to offer the plugin as a paid expansion option for CLion.
> As said in the announcement, RustRover is available as a plugin to IntelliJ IDEA during the preview period. However, we have yet to determine whether this will be the case once we’ve released RustRover. This is because we’re still not certain whether users will need the plugin or whether a dedicated Rust IDE will be sufficient. Around the release time, when we make our decision. We’ll also consider the cases when IntelliJ IDEA licenses were primarily bought for Rust development with the IntelliJ Rust plugin and which options we can suggest to our users in these cases. Please stay tuned!
https://github.com/intellij-rust/intellij-rust/issues/10867#...
In reality of course it's a bit more than just compiler support, you'd want easy interop with Javascript and Web APIs and a working debugger. With the Emscripten SDK and Chrome's and VSCode's WASM DWARF support it's looking pretty good now at least for C and C++ (but I assume the WASM DWARF debugging stuff also works for Rust, since it's the same compiler infrastructure underneath).
Leptos, as a popular recent example, suffers from one major issue (that most others suffer from too): the JSX stuff is opaque to Rust Analyzer. Code completion aside, you lose the ability to hover - massively crippling any hope of tracking down how to resolve a type mismatch.
Web Rust also has the impedance mismatch that Rust has for UI. There are several success stories - e.g. Cosmic Desktop, but I'm certain that there's more love than practicality involved.
I think part of the reason is that we are trying to shove in existing patterns - which originate from OOP languages - into Rust. In both semantic and ergonomic terms I have been bitten by trying to OOP in Rust when I was first learning it.
I think that there exists an (as yet unknown) solution to the UI problem. It's just going to look nothing like React (or Elm even).