An interesting release

Oh, well done. Actual *LOL* here.

Yeah, but it does make sense given the history. MS engineers really liked Java and the JVM and invested a bunch to make their implementation on Windows the fastest and most capable, but in doing so they made optimizations that broke compatibility with Sun Java, Sun didn't want to lose control of the Java ecosystems so Sun sued MS and introduced a compatibility test framework so they couldn't use Java trademarks or language unless they passed. There were a number of competing implementations at the time, not just MS, GNU had gcj, IBM had their own same as MS, and Blackdown Java which morphed into the OpenJDK (IIRC, it's been a while). MS engineers still liked the idea of a managed runtime so they took the engineering talent which designed their JVM and had them design a new runtime, the CLR and language to go with it, which MS submitted to standards bodies so that they wouldn't be guilty of monopolization, something they recently lost in court. Miguel de Icaza from GNOME and the commercial org Helix Code / Ximian also liked the idea of a managed runtime and liked C# which has an open standard so took on the effort to write Mono and make GTK# a supported GNOME technology, but without proprietary Windows libraries which aren't part of the language specification. WINE and other projects are more focused on re-implementing Windows stuff for cross-platform compatibility and GNOME doesn't care about Win32 or MS libraries, plus they designed the Vala language and put a lot more effort into making their C libraries robust and powerful, so MS use of ht CLR and GNOME use of the CLR are almost two ships in the night. MS did buy out the maintainership of Mono so they could improve the cross-platform compatibility of .NET, creating .NET Core and porting PowerShell to it so they can use it more on Linux servers, in competition with Enterprise Java (and I suppose to a lesser extent Python, Perl and PHP) as MS isn't really trying to "take over the world" with Windows NT Servers anymore, that ship has sailed and Linux has won. I think MS engineering really wanted to leave all the tech debt baked into Win32 (with designs going back to Win16 and the 1980s) and move to C# but they couldn't figure out the business case even when the technology was good, 3rdparty developers and customers really want long-term compatibility with legacy apps and MS wasn't able to gain leverage with Windows Phone or the Windows Store, so they abandoned a lot of the tech around .NET, which is why the joke that you can't even run Windows .NET apps on Windows because the underlying XAML/WinForms/Silverlight/whatever (I don't dev on Windows so I don't follow this closely) isn't ported to the new .NET Core runtimes. It's a shame technically because I've heard good things about the development experience, although I suppose what really killed it all off was web apps and wrappers like Electron that deprecated a huge amount of "native" app development across the industry.