Summary: Novell’s development of Mono steps outside the sandbox defined by Microsoft’s Community Promise
AS WE noted 5 days ago, the Mono developers (of which there are not many) are making Sqlite easier for Microsoft to embrace and extend (if Microsoft ever wishes to do so). Miguel de Icaza is just one among several who rave about this and yesterday he wrote about C# 4 and Mono, confirming the worries that Microsoft’s useless Community Promise (MCP) will be rendered “not applicable” as .NET continues to evolve.
“This is why projects such as Banshee are also stepping in areas of .NET which the MCP simply does not cover.”In essence, Novell already knows that Microsoft’s MCP is limited to particular packages/components and versions of C#/.NET (and their Mono equivalents). Novell can totally ignore this because it has a special and exclusionary deal with Microsoft (regarding software patents, to be more specific). This is why projects such as Banshee are also stepping in areas of .NET which the MCP simply does not cover.
For the time being, Novell’s new release of Evolution seems unencumbered by Mono, but this changes as soon as Evolution is put inside distributions and gains plug-ins [1, 2, 3]. The same goes for Novell’s Go-OO, which happens to share the same “go-” prefix as “go-evolution” and “go-mono”. It is almost as though they are all part of the same dynasty.
“The patent danger to Mono comes from patents we know Microsoft has, on libraries which are outside the C# spec and thus not covered by any promise not to sue. In effect, Microsoft has designed in boobytraps for us.
“Indeed, every large program implements lots of ideas that are patented. Indeed, there’s no way to avoid this danger. But that’s no reason to put our head inside Microsoft’s jaws.”