At best this would be an acquihire. At worst this is a defensive acquisition. I hope it doesn't happen, because nothing good can come out of it.
At best this would be an acquihire. At worst this is a defensive acquisition. I hope it doesn't happen, because nothing good can come out of it.
Nothing except that it wasn't a priority for them. Maybe it is now.
I'm pretty sure releasing a version of the .NET framework and runtime that works across platform is a little more difficult than changing the target architecture on their compiler settings (does their compiler even support different architectures?)
I'm not saying it isn't possible - just that it wasn't a priority for them. This doesn't mean they don't want or support a cross-platform .NET ecosystem. (If I recall something Miguel De Icaza wrote some time ago, the internal teams in Microsoft have been supportive of Mono.)
Do agree though that if this were an aquihire or defensive move, then it sucks for the rest of us.
And, yes, nothing stopped MS from working on an cross-platform .NET implementation before except strategic direction, but if that strategic direction were to change they'd be better off having the leading cross-platform VM and its developers in house.
LibGDX is using RoboVM these days instead of Xamarin, due to the price. Also anecdotally they found RoboVM runs even faster than Xamarin [2], despite being a young project.
[1]: http://blog.robovm.org/2014/03/robovm-0010-is-here.html
Mono is also an implementation of that standard, a cross platform one, and open sourc-ish (they do some dual licensing stuff)