So it is positive that security group is also pushing for it, alongside .NET and Core Guidelines for C++.
Now how much politic weight they are able to carry, remains an open question. If WinDev was more sympathetic towards DevDiv probably Longhorn would have actually happened, as proven by Singularity and Midori.
Rust is a completely different story. Sure, Rust's standard library treats OOM is fatal, which is the right thing for almost all application code, but it's not difficult to create Rust libraries that treat OOM as a recoverable error, or that don't allocate at all.
If the Singularity group had invented Rust instead of Sing# things might have turned out differently.
Multiple OSes have been written in GC enabled system languages.
Having a GC doesn't mean all memory is required to be GC allocated on the heap, usually the same mechanisms of a language like C++ are also available, e.g. Modula-3, System C#, D and so forth.
Joe Duffy clearly states in one of his Midori talks that WinDev did not believe in Midori, even with it running in front of them.
Longhorn would have happened if it were feasible and AFAIK it was one of the reasons for why Windows Vista took so long.
Now after Midori, and the way things turned out for UWP, we are coming back full circle with .NET 5, XAML Islands and WinUI.
RipGrep: Replace Grep and it is blazing fast
bat: Replace cat with better display and colours
exa: Replace ls with many more options
I do not have any affiliation with them, I just use them a lot
It’s unfortunate how effective editorializing is.
Because "advisory" has a specific connotation, the title you provided managed to be a lot more misleading than the post's original title.
In any case, I cannot edit the title now.
I did not notice any slowdown on a 10 years old laptop running the latest release from Windows 10, on the contrary it is quite snappy.