4 ms·

I agree. Cannot see the vast majority of C# devs moving over to Rust any time soon. The odd exception being software that needs better control of memory and pe

I agree. Cannot see the vast majority of C# devs moving over to Rust any time soon. The odd exception being software that needs better control of memory and performance. I am more interested seeing where Microsoft, in general, go with Rust in their ecosystem. Last I heard (and I have only read bits here and there) Rust is now part of the Windows Kernel (the compiler comes with it) and they have been hiring for Rust developers for their Azure platform. I dont think Microsoft are replacing C#, either. However, I would be interested to see what software they use moves over to Rust under-the-hood. For example, their their Visual Studio IDE which moved over from C++ to .NET (around 10 years ago) moves over to Rust. One thing people complain about Visual Studio is performance and being a memory hog. I would not be surprised if they experiment a Rust version. Developers... especially Windows developers... are likely to follow the footsteps of Microsoft. If their larger apps move to being Rust, can see many C# developers moving over as well for their larger-than-average projects.

sebazzz 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. That in itself is probably a huge undertaking, since it runs on .NET Framework now, probably also with a lot of C++/CLI.
- 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 ago
    Also note that Visual C++ 6.0 is going to be single threaded!

sebazzz 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. That in itself is probably a huge undertaking, since it runs on .NET Framework now, probably also with a lot of C++/CLI.

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 ago
  Also note that Visual C++ 6.0 is going to be single threaded!