Microsoft only produces the Silverlight runtime for Windows and OS X, leaving Linux support to Novell's Mono project, which produces Moonlight. Mono developers argue that Mono is not chasing tail lights, but in the case of Moonlight it very clearly is.

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.

Novell-sponsored Mono software gets extended so as to make it interconnected with Microsoft Moonlight, a "forbidden" component by Red Hat's assessment

Boycott Novell contributors explain why Mono and Moonlight are real risks

A batch of small updates on the Mono/Moonlight situation - NOVELL'S (and Microsoft's) plan with Moonlight is something that we have warned about ever since Moonlight was first announced.

ECMA is seemingly unable to offer answers regarding Microsoft Moonlight and Mono

It's time certain pro-MONOpolists faced the fact that Mono only exists to serve Microsoft. Take away Novell employees' contractual obligation to follow the company's agenda, and suddenly Mono becomes redundant.

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

gNewSense is shifting to Debian codebase, shafting Mono, and the debate about Mono and Moonlight reaches new levels