Rarely do you get something for free, and assuming that this time is different is more likely hubris.
And when you do get something for "free", it's more about making trade-offs that no one notices (JIT) or doing incredibly clever things in a layer abstracted enough that people won't have to concern themselves with what you did (language and compiler design).
As for note, all modern mobile OSes have languages with runtimes, regardless of AOT or JIT compiled, but they all required architects with guts to push them through.
The article's author's assertion is that blindly using managed code in performance-critical components is a stupid idea, and I agree.
From the article, WinFS (the filesystem), Avalon (the UI compositor and renderer), and Windows Communication Foundations (networking) were all rewritten in the then-new/unstable C# for Vista.
Given that fate of the projects, I'd say history bears it out as being a stupid idea.
The projects were killed by political reasons, not technical. Specially after what was being done with Midori, also killed by management, in spite of the technical achievements.
You can't really do this with a managed (VM) language.
Now with .NET Native, C++/CX and UWP, one can say the design of Longhorn is revenged.
The COM based infrastructure could already have been a thing, if there was a desire to collaborate during Longhorn's development.