Hacker News new | ask | show | jobs
by stephenrkell 2463 days ago
True that the CLR is not mentioned by name, but it is covered. I invite you to read the text again, and especially the following bit.

"Specifically, we should aspire to package language implementations in a way that renounces ‘one true VM’, instead allowing first-class interoperability with the host environment (perhaps at modest drop in performance), the same interoperability with other VMs past and present, and tool support which ‘sees across’ these boundaries."

The CLR simply doesn't do these things, as witnessed by the debacle of "Managed C++" and the usual FFI wrapper tedium of "explicit P/Invoke". It is a classic "one true VM", albeit more language-inclusive than a single-language VMs.

1 comments

Surely it was an _attempt_ at all these things, it just didn’t work out. For instance, I remember controversy that new Windows APIs would only be accessible via .Net.