https://blog.jetbrains.com/blog/2022/12/06/update-on-jetbrai...
Much respect to these guys for their principled stand.
Ok, I had let my CLion subscription lapse because I didn't like where they were going with the RustRover/CLion split (I do both C++ and Rust work, and would prefer one tool).
But this may make me reconsider.
Update: I gave it a quick go, and it seem to have feature parity with RustRover. Give it a shot if you haven't.
I'm 100% sure I'm not on the only team that does both Rust and C++. Rust in CLion was perfect for me.
I could get my employer to pay for both, potentially, but I like to have my own licenses for things for the purpose of doing my own open source work independent of my employer, without any ambiguity about IP or potential for conflict.
For myself ... the way they handled this (bad communication of roadmap) irritated me enough that I dusted off emacs and got myself set up with a nice configuration with lsp, company, projectile, and treemacs and made myself productive in it.