4 ms·
This was a stupid take even then. Performance in Visual Studio has become such a problem that I've renounced it entirely in favor of Rider.
by thrower123 6y ago
This was a stupid take even then.
Performance in Visual Studio has become such a problem that I've renounced it entirely in favor of Rider.
- shade 6y agoThis is where I am, too - long time .NET dev, have gotten increasingly frustrated with Visual Studio's awful performance, especially with ReSharper. I've tried taking that out given VS has a bunch of that stuff built in, but working without R# completions feels like trying to work with one arm tied behind my back. Between that and my preference for Macs for my personal laptops -- and I've been very excited at how good .NET Core has gotten on non-Windows platforms -- as well as a ~3 year sojourn working with Java 8/11 in IntelliJ, I've gotten very comfortable working with JetBrains IDEs and generally prefer them when I have the option. Structure View is great, the search is nice and snappy. The only thing that frustrates me with Rider is I don't think you can apply fixes from Roslyn analyzers at the file/project/solution level like you can in VS. We enforce our team's coding standards using those, so it's a minor pain point, but not enough to get me to stop using Rider given how much faster it is.
- tracker1 6y agoHaving worked mostly on solutions with at least one Web project in the mix, it's even worse. I absolutely love VS Code, but VS itself is a beast that I just avoid opening if I can at all avoid it. VS Code isn't quite as good on C# projects, I will admit, but still so much better (less blocking) in general. Not familiar with Rider though.