[brsiegel]

+1 on this. Previously worked in the developer tools division that builds VS, and whenever someone got assigned to work on a performance or crash bug you'd almost always wind up hearing them mutter "it's f*cking ReSharper again". The VS team has had a huge push in the last few years to improve code analysis, introspection, and refactoring (with Roslyn) specifically to try to replace / kill ReSharper. The company has no animus with JetBrains, and the team has nothing but respect for the value it's added to the ecosystem, but it's by far the biggest source of perf and crash issues in VS.

I know people feel like they just can't possibly live without it, but the refactoring tools in VS nowadays are much better, so I encourage folks to test drive by going a couple weeks without installing ReSharper. If you still really miss it and are willing to pay the performance penalty to have it after that, go for it. But give VS a fair shake without it.

[torginus]

Resharper is kind of a dog in terms of performance, and I think it's a major source of performance issues under VS - especially with large project.

One of the reasons for this is you can't turn off the Roslyn-based MS engine in VS (which IMO is reasonable, since it's needed for a lot of stuff) so there are always 2 code analysis engines running.

That's one of the main selling points of Rider Imo, that it doesn't run 2 completion engines simultaneously, which makes it much faster.

Unfortunately Resharper is still far superior to VS with the quality and quantity of built-in refactorings.

Another thing with Resharper is that it seems to run synchronously, meaning if you type something and press the completion button, the suggestions always pop-up. A major pain point in previous VS versions is that this wasn't the case with the built-in engine.

Sometimes you just pressed the autocomplete button and nothing happened, because VS was still parsing your code.

Thankfully 2022 fixed this, and this is one of the reason I would never consider going back to the older versions.

[WorldMaker]

> One of the reasons for this is you can't turn off the Roslyn-based MS engine in VS (which IMO is reasonable, since it's needed for a lot of stuff) so there are always 2 code analysis engines running.

Roslyn is extremely well tuned. (Anecdotally in any IDE including VS Code without ReSharper it's performance is incredible and hardly noticeable.) ReSharper's performance problems are ReSharper's performance problems.

Blaming ReSharper's performance on Roslyn is just as wrong as blaming ReSharper's performance on Visual Studio. It's pointing the finger at the wrong thing in the stack.

Of course that's a big selling point for Rider. It's incredibly wonderful marketing luck that almost all of ReSharper's performance problems get blamed on Visual Studio itself or on Roslyn and almost never directly on ReSharper. As long as people keep pointing the fingers away from the plugin, JetBrains gets just about free marketing from every VS performance complaint real or imagined. Their incentives aren't aligned to improve ReSharper performance when "everyone" just answers "Just switch to Rider already" because they mistakenly blame Visual Studio rather than the ReSharper's own engineering.