Yes and No. Tons of core C++ Windows stuff will be Rust based. C# will be more suited for some control panel/configuration settings where the performance won't matter much, as they are seldomly used. The rest will be pretty much Rust instead of C++.
That isn't what many reports assert, in fact the roadmap for Visual Studio is being the best C# and C++ plus AI IDE, see latest roadmap announcements for VS 2027.
Apparently outside WinUI efforts, that many don't care about, there isn't much going on, the Rust action is all on Azure side.
OFC C# it's tied to VS, it's basically the platform. And, still, Windows internals rewritten in Rust are the best bet. Even the IDE being rewritten in Rust would outperform C# in speed while giving more security.
Rust for systems programming, C# for non-performing bound tasks (control panels, launchers, light gaming, GUI's on top of Windows CLI tools) and C++ for raw performance. And, still, I won't let any modern codec for A/V to be written in C/C++ for obvious reasons. And I am a diehard Unix+C user in the infamous N270 netbook. but dark times with automatic AI attacks are comming ahead. That's why I migrated from Mutt to Aerc, while keeping my Maildir and msmtp/isync.
At least I will be able to reencode potential harmful media for 420p/720@30FPS for the netbook in the NUC if FFMPEG (or FFMPEG based tools) were converted into Rust without hitting several vulns, because they will be everywhere:
- qemu/libvirt
- imagemagick/graphicsmagick, both the tools and libraries
- any libav* codec/parser
- libpng/libgif and similar
- zip/7z/tar/pax
- PS/PDF, of course. Especially PS, for obvious reasons.
- Some DOC/XLS formats pre DOCX are raw memory dumps and maybe they can be partially executed.
- Some other formats can act like a mini-VM bytecode too, such as RAR.
I even compiled Bubblewrap too so I can jail some of these, and yet I don't trust them 100%. Some recent exploits bypassed the chroot like nothing.
Other than a few examples given in the past, the Rust adoption among WinDev doesn't seem to be really taking off like in Azure.
Indeed C# is getting more low level coding features, and the unsafe memory model is being redone in .NET 11 for a reason.