[tyrion]

The fact that Microsoft keeps saying it wants to move away from C/C++ is great IMHO.

> Microsoft c++ continues to be written and will continue to be written for a while

I interpret this as saying that they cannot instantaneously convert all their existing code to Rust, and it seems fair enough. However, it seems a little odd to start new projects in C/C++ when you are publicly saying it's the wrong thing to do.

Infact, just a little over a month ago they announced a new QUIC implementation written in C/C++ (MsQuic)

Is this to be expected since Microsoft is such a big company? Or maybe that lib is not important and is not going to be used in, say, Edge?

Moreover, isn't networking code the worst kind of code to write in C/C++ (I am thinking of heartbleed for example)? I would really love some explanation.

[adolfojp]

The more I learn about Microsoft the more this joke makes sense:

https://en.wikipedia.org/wiki/Manu_Cornet#/media/File:%22Org...

[pjmlp]

Which is why they are the main drivers for C++ Core Guidelines, and have contributed the initial effort of a C++ lifetime analyses to clang, while making it available in all Visual Studio editions, including Community.

They are quite clear that a constraint version of C++ still gets to play in a secure world.

And while Azure Sphere still gets to be written in C (due to Linux kernel), it has a security layer (Pollonium) that takes care of bad code.

Finally, since they failed to move people into UWP programming model, sandboxing has been coming into Win32 as well, to the point that on Windows 10X, everything is sandboxed, including Win32 apps.