It will come down to preference. The best tool for the job is the one you're familiar with. But if you've never tried Rider, I think it's good advice to try it and form your own opinion.
You might like the built in code completions, with the included local LLM. If you've used the Resharper plugin for Visual Studio, you might like that those features come included in Rider. Same with DotPeek, if you like to decompile dependencies to view implementation details. You might also like Rider's built in 3 way merge with magic wand to auto resolve easy conflicts.
If you also develop outside dotnet ecosystem, you might like that Rider has the same UI as Idea (java development) and Webstorm (frontend development), so switching between them is more familiar.
One thing I don't like about Rider is its inline type hints. I think they clutter the code and I usually disable them.
I haven't gone back to Visual Studio in a while, so I can't offer an honest comparison since my experience is a bit outdated.
(But to be honest, I don't really use Rider too much nowadays either. I've mostly switched to VSCode. So take this with a grain of salt. And apologies I didn't address the items you listed. I just wanted to point out the items I personally took note of)
You might like the built in code completions, with the included local LLM. If you've used the Resharper plugin for Visual Studio, you might like that those features come included in Rider. Same with DotPeek, if you like to decompile dependencies to view implementation details. You might also like Rider's built in 3 way merge with magic wand to auto resolve easy conflicts.
If you also develop outside dotnet ecosystem, you might like that Rider has the same UI as Idea (java development) and Webstorm (frontend development), so switching between them is more familiar.
One thing I don't like about Rider is its inline type hints. I think they clutter the code and I usually disable them.
I haven't gone back to Visual Studio in a while, so I can't offer an honest comparison since my experience is a bit outdated.
(But to be honest, I don't really use Rider too much nowadays either. I've mostly switched to VSCode. So take this with a grain of salt. And apologies I didn't address the items you listed. I just wanted to point out the items I personally took note of)