Earlier quoted context omitted.
I've got no idea why Microsoft was going apesh· for bytecode all of a sudden. Delphi probably was one of the main reasons. It was a lot better for Windows 32 development than VB and there were projects to port it to Linux. Microsoft then recruited Delphi leads, settled a long running suit with Borland (with the fallout of stopping Delphi for Linux development) and finally created a platform where they keep control, u…
Java was the reason. COM Runtime was going to be native (Ext-VOS), but then they decided to go VM path and .NET was born. https://blogs.msdn.microsoft.com/dsyme/2012/07/05/more-c-net... If you read Don Syme blog entries about .NET history, you will see a few similarities with WinRT. Just with .NET metadata instead of the old COM type libraries. So the double bet on COM since Vista was a bit like WinDev's revenge. How…
Who do you think had more weight in the decision, this guy or the chief architect for .NET that came from Borland? Of course Java was the model for the VM thing, but that's the what, not the why, the reason they, in the words of the gp, went apesh··· with the bytecode thing.
Actually I can neither be in the mind of whoever made the call, just make an educated guess, but at least it has a base on facts that I was paying attention to at that time.