3 ms·
> I think the performance problems of Visual Studio are more in regard to architecture and legacy than the platform it runs on, though running it modern .NET pr
by masfoobar 3y ago
> I think the performance problems of Visual Studio are more in regard to architecture and legacy than the platform it runs on, though running it modern .NET probably could achieve various performance improvements
I dont know how true this is -- but I can be wrong.
I mean, you run Visual C++ 6.0 on todays machines. It is incredibly fast at loading and the debugger is instant when you step in/over.
Sure, Visual C++ 6.0 is not doing various things that Visual Studio 2022 is. It isn't doing API calls onload and other things. However, you debug a program. The different is obvious.
I am not going to say/write that "it is because it moved away from C++ to .NET" but these slowdowns appear to start happening around the timeframe. At least, from my experience.
Maybe the truth is the architechture and/or legacy codebase. Also, it might be a huge undertaking to experiment on Rust. However, if any Company has the money and resources to do it.. it will be Microsoft.
Personally I am "OK" with Visual Studio and performance 80% of the time. However, I am slowly moving away from Visual Studio since .NET Core came out. Yes, I use it for debugging but for coding, stick to me preferred text editor now with omnisharp.
- masfoobar 3y agoAlso note that Visual C++ 6.0 is going to be single threaded!