I prefer VS but for the performance, I use VS Code. Unable to work in Rider on 32 GB RAM.
Good IDE but they ignored bugs and serious performance problems for too long. The main project I'm working on isn't even that big, maybe 1M SLoC in total, most of them C#, and Rider really struggles with it even on good hardware.
This forced some architectural changes to satisfy the machine (breaking out libraries where they weren't necessary, running code analyzers only in CI, not during development, etc).
So I don't miss the experience.
MS finally have a language server (still in preview, but it works fine) which can be attached to helix in a couple of lines, and that + good knowledge of Unix command line tools is more than enough now.
There is a gigantic difference between "technically possible", "practical" and "enjoyable". I had some junior engineers hounding my ass about using ORMs and the liability of manual schema management until they saw how sqlproj and sql compare work in VS proper. You can certainly string this along with 3rd party and custom using other IDEs, but then you don't have as much time and energy to focus on the actual problem. Maintaining a stack just to maintain your stack is pretty crazy to me. I'll happily pay the idiot tax at Home Depot for the Milwaukee option so I can place an invariant on this part of the problem space. I never want to be in a position where I can blame my tools for a bad work product.
But I'm on linux now. If I wanted to pick up back up then what should I be using?