It's obvious that things that shouldn't do a lot of work, do in fact do work. Like if I press Ctrl+C on some selected text. I simply expect it to put the text into the clipboard. But sometimes it will stall, put a dialog on the screen telling me it's doing some formatting and I need to wait! What the hell is it formatting?
Every member of my team is sick of it and it's negatively affecting our productivity, so if Rider is good then bye bye Visual Studio.
Obviously a 32bit app could run a number of sub app domains, so it can still make use of more than 2gb. I think ultimately though is it's not the resource that's the issue, it's the buggyness of the system. It just feels unfinished, and it seems there's some lazy decisions made in implementation ... the formatting error on Ctrl-C sounds like it's doing too much work; other things like if I try to download a publicly available nuget package, through the god awful UI, I have the source setup as nuget.com - it then pops up a dialog asking for my credentials to my company nuget server! If I cancel it, guess what, it fails to get the package from the web.
I have a strong suspicion that it's talking to the net too often generally (I have a slow broadband connection, so I see areas that are clearly doing too many round trips).
I feel it seemed to really start going downhill when Roslyn became the compiler (which I assume is running most of the tooling). I don't know if that's anything to do with it, but I assume they had to rewrite a lot of the core components when Roslyn came along.
2015 wasn't great, 2017 is really bad. Waiting several years for them to finish the project properly is taking its toll on my confidence in a product I've used in one form or another since 1994
Dave twitter.com/davkean