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)

It is definitely more performant in my experience. Occasional hiccups happen as well, but way less than with VS. Please note my experience with VS 22 is a bit dated because I moved to Rider a few versions ago (probably 17.8 or 17.9). Additionally, I haven't really used VS without the ReSharper plugin extensively so that's what I can compare Rider to.

Regarding your points:

> MAUI

No personal experience yet unfortunately on my part

> Code completion

At least on par, basically ReSharper with a few extras. Navigation and refactoring is great and comprehensive.

> IIS

Also no personal experience

> Debugging

Great debugger IMHO. Matches VS, predictive debugging is nice (deemphasizes branches it knows won't run), breakpoint conditions are great (only break on a certain thread, after another breakpoint had been hit, after n hits, ...), shows return values in the watch list automatically, etc.

> Look & feel

Probably personal preference: I prefer its more modern and focused look over VS. If you're into that, its Vim emulation plugin is superb.

> WPF

Not its strong suit. VS is way better here. Rider only has a preview. Annoying: it doesn't use themes for DevExpress-libraries correctly in one project at work.

> file explorer

Pretty much like VS

> Git integration

In my experience nicer than in VS. Exposes git's features more easily than VS. Take it with a grain of salt because I use the CLI mostly anyway.

I hope this helps a bit. But you're probably better off trying it for a while if you can.

Rider is a full-fledged, cross-platform C# IDE on par with Visual Studio (full version, not code). I have used a little bit of Rider and other Jetbrains products. It was some time ago, so take it with a grain of salt. On my windows machine Rider felt a bit snappier. Debugging was also great. Pretty much the same as Visual Studio. Code completion, code navigation and refactoring is at least on par if not greater with that in Visual Studio. Git integration is there, file-explorer is there. Haven't used WPF/XAML so don't know about that. Generally speaking if you buy the license for all Jetbrains' products to use WebStorm or other stuff they offer I think it is worth it. Or maybe you would want to develop C# apps on mac or linux then Rider is the go to. Other than that I wouldn't bother buying the license.