[tdrp]

I don't know what they did in VS2019 but there was clearly a ridiculous perf hit in many modules, especially Intellisense related.

While I sort of liked the AI-predictions, they introduced a serious lag in typing and every couple of seconds typing would nearly freeze. After I turned those off, typing became smoother but still slightly laggy (sort of like typing on a remote terminal on the other side of the world), and the predictions would pop up much slower than VS2017.

Lots of other perf issues like "Find in files" being 3x slower than in VS2017. Or adding a new class to a file wastes several seconds looking up templates somewhere. I saw dozens of bugs filed for these issues over the past few months and most were resolved as "Fixed" (allegedly) or "No repro" but in practice the IDE perf is still IMO unacceptable.

I really hope they fixed that stuff with VS2022.

[scpedicini]

I had the same experience moving from visual studio 2017 to visual studio 2019. I tried disabling every possible IntelliSense related feature and there was always a small but perceptible amount of input latency that drove me crazy.

Eventually I was forced to switch over to jet brains rider and I haven't looked back since, which is a shame because I really enjoyed using the previous versions (2010, 2012, 2015, and 2017).

[vidanay]

Or my favorite....closed due to lack of community response.

[tracker1]

Yeah.. I mean, I understand metrics... but there are some things that just won't see broad complaints, but are indeed issues. Not everyone will be a squeaky wheel, doesn't mean those "less interaction" issues aren't meaningful/bad. Not to mention having to create yet another profile to even interact with the issues... if an issue is created, I won't always login even to give a +1/heart on something.