I was going over an old Groklaw posting that got me thinking about Microsoft and it’s .NET Agenda. I decided to do more research and took a look at the Comes vs Microsoft documents again but from the perspective of the current Mono issues. I am even more convinced that Mono and Moonlight do nothing but help Microsoft win against competing platforms.

In the same vein, if Novell and Microsoft call it "Microsoft Moonlight", does it make Moonlight developers de facto Microsoft employees?

Moonlight hype comes from Microsoft's direction, as usual

More disturbing details about Moonlight are unleashed

A new story of migration to Microsoft (due to Apple's reliance on Microsoft) offers an important lesson about the purpose of Novell's Mono and Moonlight

I noticed a comment thread on Groklaw about Moonlight, with a link to the license terms on Microsoft's website. They call it Covenant to Downstream Recipients of Moonlight - Microsoft & Novell Interoperability Collaboration . A comment by Microsoft's Brian Goldfarb on Dana Blankenhorn's article about Novell being a lead pony for Silverlight started the discussion originally.

Moonlight’s cold reception was mentioned briefly just a couple of days ago, but let’s emphasise again why GNU/Linux users must not accept it; instead, they need to complaint or protest against Webmasters that adopt such ActiveX-like embrace & extend strategies. Don’t let Microsoft journalists lie to developers by saying that there is “Silverlight for Linux” because there isn’t.

Moonlight, the de facto open-source implementation of Microsoft's Silverlight platform for Linux that leverages Mono, is nearing its 3.0 release. Moonlight 2.0 was just released a half-year ago, but Moonlight 3.0 Preview 7 was just released and it's offering up more features.

Timely perspective on Apple, Microsoft, and the substitution of "Linux" with Android (Google's trademark)