Comment by icar
1 year ago
"It just works" is precisely why I use Jetbrains products. I'm amazed they are not that common in many developer communities. They are amazing tools.
1 year ago
"It just works" is precisely why I use Jetbrains products. I'm amazed they are not that common in many developer communities. They are amazing tools.
Personally, it’s because they are not open source and not as fast.
Yesterday RustRover became so unresponsive that the UI would freeze for more than 15 seconds (as reported by their exception notifications) and completions would take 5 seconds to appear and be wrong or lacking most times.
I was seriously doubting the internal Rust engine (they don’t use rust-analyzer or LSP), so I switched to VSCode with the rust-analyzer extension, and the same happened there too, although no freezing. Turns out some of my types were 80k characters long, and ‘cargo clippy’ was taking ~900 seconds of one core pegged at 100% for rustc. Oops.
Now I know what they mean when complaining about super long compile times on Rust, and I wasn’t even doing async :)
> Turns out some of my types were 80k characters long,
I know Rust uses name/symbol mangling but what sort of type declaration in Rust ends up with that long names ?
1 reply →
Rust Rover is terrible, they made it free and I still dont use it, Zed is great for Rust.
And not cheap either if you want the "ultimate" editions.
They absolutely are the state of the art. At the same time, opening just three or four medium size projects brings the editor to it’s knees on my M3 Max.
I like having many projects open.
Webstorm kept crashing and grinding to a halt on my codebase. Vscode and neovim didn't have that issue so that's what I use now.
The support for remote or in-docker development has been an issue, personally. Terminal editors and VSCode are much more “it just works” in this regard, especially when joining codebases that used docker to isolate all the dependencies to actually run tests/services for local dev.