Are you a sponsor of this guy after all? Getting paid to respond to all web comments regarding it? It's quite weird why you have been responding to all these posts with all the passion.
With that said... I work at Microsoft on Windows OS, and the main point that was mentioned is indeed true: this is a claim of this engineer only and his team, and it just seems to be a plan totally misaligned with Windows OS vision of how things should be in 10 years. We won't get rid of C++ code anytime soon, the goal is to keep in hybrid state, not to get rid of things. This is unfeasible to do in mature products given all Windows OS processes to ship code.
I wish, I just happen to be more aware of what is happening at Microsoft Research than the regular HNer, thus I clarify with passion.
A little money wouldn't do any harm, though.
And since you are here, some of us dislike the C++ vs .NET narrative from the Windows team, Windows 7 .NET bindings being dropped, refusal for .NET DirectX Bindings like Apple and Google do with their 3D APIs, the way UWP tooling went down the drain, and would welcome an improvement on the state of affairs.
Does the kernel team only use Rust for new code? I heard that Mark once said that no new C/C++ code is allowed but wondering if it's for everything or just part of the codebase.
