▲ | pjmlp 7 months ago | ||||||||||||||||
Disregarding the rumor, it is quite public information that on Azure side, C and C++ are now only allowed for existing code bases, or scenarios where nothing else is available. Meanwhile on Windows side, it was made officially at Ignite that a similar decision is now to be followed upon Windows as well. Here the official stuff, so whatever happens to MSVC is secondary, https://azure.microsoft.com/fr-fr/blog/microsoft-azure-secur... https://blogs.windows.com/windowsexperience/2024/11/19/windo... | |||||||||||||||||
▲ | _huayra_ 7 months ago | parent | next [-] | ||||||||||||||||
> in alignment with the Secure Future Initiative, we are adopting safer programming languages, gradually moving functionality from C++ implementation to Rust. This seems like one hell of an initiative for the Windows OS. That is millions of lines of C++ code, often with parts from waaay back. A friend who works on one of the OS teams told me that his team got a boomerang hire that worked on Windows back in the 90s and he was still finding parts of his code in there! I hope this corporate interest bodes well for Rust though. It seems like for C++ it really caused a schism over the ABI break issue where Chandler et al were basically rebuffed finding some timeline to break it, and then Google dropped all their support on the committee in favor of Carbon, Rust, etc. | |||||||||||||||||
| |||||||||||||||||
▲ | nitwit005 7 months ago | parent | prev [-] | ||||||||||||||||
They've made statements like that for a long time now. But they've never escaped using C++ when performance matters. The game dev roles very clearly ask for C++, for example. Rather, it seems that as computers have gotten faster, there's been more places where safety is preferable to performance. | |||||||||||||||||
|