Well, what I found to be great on it, is the ability to see even Blueprint references to code – so I can see a list of all blueprints that are dependent on a particular piece of code pretty quickly. As well, once it’s indices are built (which took a couple of days) it is usually much, much faster at finding various things than VS intellisense. Which makes it very good for exploring things. Sadly, all editors seem to be missing a feature that would be utterly amazing – “Find In All Super/Subclasses”. That was a feature of an editor that was used in the UnrealScript days, and it was amazing. It blows my mind that no one has done that in any other editor that I’ve yet seen.
As far as writing, the entire editor feels like a super clunky 1995 era Java app (which is possibly what it’s based on) that is extremely slow, has a completely foreign keymap, and a mystifying user interface based on said 1995 ideas “Java runs on everything, so let’s make an interface that doesn’t actually resemble the native OS”.
As far as debugging goes, the debugger is just … awful. It’s hard to quantify, but the debugger in Rider more closely resembles the extremely difficult to operate design of Visual Studio Code’s debugger versus the extremely easy to use Visual Studio debugger.