EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

07.17.09

Free Software Foundation Discourages Dependence on Mono, Dismisses Microsoft Community Promise

Posted in FSF, GNU/Linux, Microsoft, Mono, Patents at 8:29 am by Dr. Roy Schestowitz

Last week, Microsoft extended the terms of their Community Promise to implementations of the ECMA 334 and 335 standards. You might think this means it’s safe to write your software in C#. However, this promise is full of loopholes, and it’s nowhere near enough to make C# safe.

Why Worry About C#?

Since we published Richard’s article about Mono last week, some people have been asking us why we’re expressing special concern about free software developers relying on C# and Mono, instead of other languages. Sun probably has patents that cover Java. Maybe IBM has patents that cover C compilers. “Shouldn’t we discourage the use of these too?” they ask.

It’s true that all software patents are a threat to developers—but that doesn’t mean that all software patents are equally threatening. Different companies might have patents that could be used to attack other languages, but if we worried about every patent that could be used against us, we wouldn’t get anything done. Microsoft’s patents are much more dangerous: it’s the only major software company that has declared itself the enemy of GNU/Linux and stated its intention to attack our community with patents. If Microsoft designed a patent trap into C#, that is no more than what it said it would do.

The company has been quite clear about its intentions since late 2006. At a user conference in November that year, Microsoft CEO Steve Ballmer said, responding to a question about their patent agreement with Novell:

… the fact that [GNU/Linux] uses our patented intellectual property [sic] is a problem for our shareholders. We spend $7 billion a year on R&D, our shareholders expect us to protect or license or get economic benefit from our patented innovations. So how do we somehow get the appropriate economic return for our patented innovation…?

(Seattle Post-Intellegencer, The Microsoft Blog, “Ballmer on Novell, Linux and patents,” November 16, 2006.)

A few days later, an interview with Microsoft President Bob Muglia was published, and he made it clear that they considered C# one of these so-called “patented innovations:”


There is a substantive effort in open source [sic] to bring such an implementation of .Net to market, known as Mono and being driven by Novell, and one of the attributes of the agreement we made with Novell is that the intellectual property [sic] associated with that is available to Novell customers.

(eWeek.com, “Microsofts Muglia Talks Longhorn, Novell and Java”, November 17, 2006.)

They’ve been turning up the heat ever since. In May 2007, Microsoft followed all this up by announcing in a Fortune magazine interview that they believed GNU/Linux infringed 235 Microsoft patents. And recently they made it very clear that these were not idle threats: the company sued TomTom for using the VFAT filesystem implementation in the kernel Linux without buying a license from it.

All of this can’t simply be brushed aside. These are statements and actions made at the highest executive levels of the company. Using patents to divide and conquer the free software community is a fundamental part of their corporate strategy. Because of that, C# represents a unique threat to us. The language was developed inside Microsoft, so it’s likely they have many patents to cover different aspects of its implementation. That would make free software implementations of C#, like Mono, an easy target for attack.

“The Community Promise does nothing to change any of this.”The Community Promise does nothing to change any of this. Microsoft had an opportunity to take action and demonstrate that it meant us no harm with C#. Instead, they took meaningless half-measures that leave them with plenty of opportunities to hurt us.

Incomplete Standards

The ECMA 334 and 335 specifications describe the core C# language, including information about standard libraries that must be available in any compliant implementation. However, there are several libraries that are included with Mono, and commonly used by applications like Tomboy, that are not required by the standard. And just to be clear, we’re not talking about Windows-specific libraries like ASP.NET and Windows Forms. Instead, we’re talking about libraries under the System namespace that provide common functionality programmers expect in modern programming languages: binary object serialization, regular expressions, XPath and XSLT, and more.

Because these libraries are not defined in the ECMA specifications, they are not protected in any way by Microsoft’s Community Promise. If this were the only problem with the promise, it might be safe to use applications that avoid these libraries, and stick to what’s in the standard. But even the code that’s covered by the promise isn’t completely safe.

Figuring Out What’s Necessary

The Community Promise only extends to claims in Microsoft patents that are necessary to implement the covered specifications. Judging just by the size of its patent portfolio, it’s likely that Microsoft holds patents which a complete standard implementation probably infringes even if it’s not strictly necessary—maybe the patent covers a straightforward speed optimization, or some common way of performing some task. The Community Promise doesn’t say anything about these patents, and so Microsoft can still use them to threaten standard implementations.

Moving the Goalposts

“The Community Promise does not give you any rights to exercise the patented claims.”Let’s say you’ve written an implementation of one of the specifications covered by the Community Promise, and you want to determine whether or not you’ll be sued for infringing a certain Microsoft patent. The necessity question already makes it difficult enough to figure this out. But even if you manage it, you should make sure you check again tomorrow, because the Community Promise might not protect you then.

The Community Promise does not give you any rights to exercise the patented claims. It only says that Microsoft will not sue you over claims in patents that it owns or controls. If Microsoft sells one of those patents, there’s nothing stopping the buyer from suing everyone who uses the software.

The Solution: A Comprehensive Patent License

If Microsoft genuinely wants to reassure free software users that it does not intend to sue them for using Mono, it should grant the public an irrevocable patent license for all of its patents that Mono actually exercises. That would neatly avoid all of the existing problems with the Community Promise: it’s broad enough in scope that we don’t have to figure out what’s covered by the specification or strictly necessary to implement it. And it would still be in force even if Microsoft sold the patents.

This isn’t an unreasonable request, either. GPLv3 requires distributors to provide a similar license when they convey modified versions of covered software, and plenty of companies large and small have had no problem doing that. Certainly one with Microsoft’s resources should be able to manage this, too. If they’re unsure how to go about it, they should get in touch with us; we’d be happy to work with them to make sure it’s satisfactory.

Until that happens, free software developers still should not write software that depends on Mono. C# implementations can still be attacked by Microsoft’s patents: the Community Promise is designed to give the company several outs if it wants them. We don’t want to see developers’ hard work lost to the community if we lose the ability to use Mono, and until we eliminate software patents altogether, using another language is the best way to prevent that from happening.


Copyright © 2004, 2005, 2006, 2007, 2008, 2009 Free Software Foundation, Inc. Privacy Policy.

Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this notice is preserved.

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

11 Comments

  1. eet said,

    July 17, 2009 at 9:22 am

    Gravatar

    “…this was brought to you via ‘Roy-Broadcasting’; now in fabulous, new one-dimensionality…’

  2. Dylan McCall said,

    July 17, 2009 at 11:30 am

    Gravatar

    I like the FSF’s article, but here’s my issue with it: It is all about patents.

    Microsoft says GNU / Linux infringes on 235 of their patents. They have, thus far, failed to communicate what those patents are. They are trying to coerce us into a standstill by making people afraid of touching GNU / Linux either as a developer or a user. That is immoral.

    Saying “people shouldn’t use Mono because it infringes on patents” is complete garbage, because clearly GNU / Linux infringes on patents in the same way, and also lacks patent protection. Ultimately, Microsoft wants to sue GNU / Linux users. That won’t stop me, or anyone else, from using it.
    This is the case for any software development down the line, too, free or otherwise. The only difference with Mono is it’s a smaller bit of code than the whole of GNU / Linux, so it’s easier to point at it and say “this one product infringes so we should be afraid.” You can’t do that for the entire operating system.

    I guess that’s the thing I don’t understand, and I bet I’m not alone. Roy, or anyone else: I would love to see something convincing. Why should I care so much about patents here, but ignore the issue elsewhere? Aren’t we kind of playing along with Microsoft’s scheme here?

    Roy Schestowitz Reply:

    Patents ought to be just a small portion of this discussion, in my eyes. Mono is about Microsoft controlling FOSS by APIs, not just patents. It’s a strategic issue, not just a legal issue.

    BTW, Groklaw has more overage of this and it adds:

    I think that there’s a major missing element to the list of requirements …, before you can consider using C#, and that is a commitment to ensuring that future standards are based on the same set of promises.

    “At the moment, even if all the conditions above were satisfied and it were safe to use C#, there’s no guarantee that it’s not an evolutionary dead-end for FOSS. Languages exist in a context, and they have to change and evolve to remain useful in a changing landscape. But there’s no commitment that I’ve seen from MS to keeping the future safe for FOSS. “

    nachokb Reply:

    Dylan,
    I disagree with this part of your reply:

    > “people shouldn’t use Mono because
    > it infringes on patents”

    That’s not the problem. If you want to use them, by all means use it. Mono is a fine piece of software and no doubt it’s useful for many people.

    The problem is that there is a seemingly powerful lobby campaign to include it in distributions which are renowned for respecting freedom.

    And one of the main problems with patents is the power it gives to established players to influence negatively a market (in billg’s own words, even). Let’s not forget that the real danger of patents is not the ability to shut down products or competitors (which would be too obvious), but the ability it gains powerful players to sow doubt or veiled threats.

    On the other hand, the exposure of Mono to specific patents is undoubtedly larger, than, say, the Linux kernel. Of course any software is exposed to stupid patents (that’s what they were designed for, after all). But Mono is specificly a reimplementation of technologies dear to the main monopolist/patent troll. It’s about credibility; if MS says that the LK is violating their patents for some memory management hat trick, they’ve got a lot to prove, and that would only be useful if they went ahead and went to a court (which is costly, even to the monopolist, be it money, PR, time); OTOH, just saying “Mono violates .NET patents” implicitly gives credibility and is easier to sell to the media (and, ultimately, affects the prospects of going to court).

    Furthermore, Ubuntu forum’s moderators showing one-sided behaviour by shutting down any mention of Mono which could be remotely interpreted as a negative or even questioning its holyness (while their users vote against Mono) and shouting FUD is troublesome to all of us Ubuntu users.

    Sorry for the length…

    nachokb

    Roy Schestowitz Reply:

    Dylan,

    nachokb addressed some of the most important points, including the perceived (and real, by design) similarity between .NET and Mono. Remember that SCO marketed its lawsuit to the media by showing UNIX-Linux similarities.

  3. aeshna23 said,

    July 17, 2009 at 12:20 pm

    Gravatar

    Saying “people shouldn’t use Mono because it infringes on patents” is complete garbage, because clearly GNU / Linux infringes on patents in the same way, and also lacks patent protection.

    This isn’t true. Just because Microsoft says GNU / Linux infringes on 235 of their patents, doesn’t mean that Microsoft is telling the truth or when it is telling the truth that the patents will hold up in court. Furthermore, no one outside of the Microsoft has a clue exactly what Microsoft is talking about. In the case of Mono, we know that Microsoft does have relevant .Net patents, and that these patents are likely to be of much higher quality, since Mono imitates .net. Also, courts tend to uphold patent infringement charges more frequently when the alleged infringer admits to imitating.

    eet Reply:

    What you’re basically saying is that the risk of bein sued over an unknown patent is preferable over the legally binding promise not to be sued over a known patent.

    eet Reply:

    To clarify; I wouldn’t give a damn about patents either way – but Microsoft got YOU so indoctrinated that you’re worrying over patents all the time.

    Now, this should really worry you.

    Roy Schestowitz Reply:

    Don’t forget In Re Bilski and its ramifications, either.

  4. JohnD said,

    July 18, 2009 at 5:14 pm

    Gravatar

    I find it interesting that the post does not mention if the CP is legally binding or not.

    Roy Schestowitz Reply:

    Agreed. There are other criticisms raised in Groklaw.

What Else is New


  1. Links 19/8/2019: Another Linux 5.3 RC, OpenSUSE's Richard Brown Steps Down, Slackware Creates Patreon Page, Qt 6 Initiated

    Links for the day



  2. Speaking Truth to Monopolies (or How to Write Guest Posts in Techrights)

    We need to have more articles tackling the passage of all power — especially when it comes to software — to few large monopolies that disregard human rights or actively participate in their abolishment in the digital realm



  3. Guarding and Rescuing the FSF Titanic: Free as in Speech

    "While a new breed of so-called anarchists campaign against expression that even the state allows, people are also foolishly overplaying the relevance of the state to free speech issues -- as if it's not a freedom issue when a project is increasingly thought-policed, because the thought-policing isn't on a state level."



  4. Toxic Culture at Microsoft

    Racism, intolerance, sexism and bullying are rampant at Microsoft; but Microsoft would rather deflect/divert/sidetrack to Google and so-called 'GAFA'



  5. Guarding and Rescuing the FSF Titanic: Introduction

    "The FSF isn't just threatened, it will hit a large iceberg in the future that changes it permanently."



  6. Linux Journal and Linux.com Should Have Been Kept Going

    There's apparently no good explanation for the effective shutdown of Linux Journal and Linux.com; London Trust Media Holdings (LTMH), owner of Linux Journal, saw numbers improving and the Linux Foundation, steward of Linux.com, is loaded with money



  7. 2019 Microsoft Glossary

    How Microsoft internally interprets words that it is saying to the public and to the press



  8. 2019 Surveillance Glossary

    Distortion of technical and nontechnical terms in this day and age of '1984'



  9. Openwashing Report: It's Getting Worse, Fast. Everything is Apparently 'Open' Now Even Though It's Actually Proprietary.

    The latest examples (this past week's) of openwashing in the media, ranging from 5G to surveillance



  10. GitHub is a Dagger Inside Free/Open Source Software (FOSS); This is Why Microsoft Bought It

    A year later it seems pretty evident that Microsoft doesn’t like FOSS but is merely trying to control it, e.g. by buying millions of FOSS projects/repositories at the platform level (the above is what the Linux Foundation‘s Jim Zemlin said to Microsoft at their event while antitrust regulators were still assessing the proposed takeover)



  11. Microsoft Grows Within and Eats You From the Inside

    Microsoft entryism and other subversive tactics continue to threaten and sometimes successfully undermine the competition; Microsoft is nowadays doing that to core projects in the Free/Open Source software world



  12. Links 18/8/2019: New KNOPPIX and Emmabuntus Released

    Links for the day



  13. Links 17/8/2019: Unigine 2.9 and Git 2.23

    Links for the day



  14. Computer-Generated Patent Applications Show That Patents and Innovations Are Very Different Things

    The 'cheapening' of the concept of 'inventor' (or 'invention') undermines the whole foundation/basis of the patent system and deep inside patent law firms know it



  15. Concerns About IBM's Commitment to OpenSource.com After the Fall of Linux.com and Linux Journal

    The Web site OpenSource.com is over two decades old; in its current form it's about a decade old and it contains plenty of good articles, but will IBM think so too and, if so, will investment in the site carry on?



  16. Electronic Frontier Foundation Makes a Mistake by Giving Award to Microsoft Surveillance Person

    At age 30 (almost) the Electronic Frontier Foundation still campaigns for privacy; so why does it grant awards to enemies of privacy?



  17. Caturdays and Sundays at Techrights Will Get Busier

    Our plan to spend the weekends writing more articles about Software Freedom; it seems like a high-priority issue



  18. Why Techrights Doesn't Do Social Control Media

    Being managed and censored by platform owners (sometimes their shareholders) isn’t an alluring proposition when a site challenges conformist norms and the status quo; Techrights belongs in a platform of its own



  19. Patent Prosecution Highways and Examination Highways Are Dooming the EPO

    Speed is not a measure of quality; but today's EPO is just trying to get as much money as possible, as fast as possible (before the whole thing implodes)



  20. Software Patents Won't Come Back Just Because They're (Re)Framed/Branded as "HEY HI" (AI)

    The pattern we've been observing in recent years is, patent applicants and law firms simply rewrite applications to make these seem patent-eligible on the surface (owing to deliberate deception) and patent offices facilitate these loopholes in order to fake 'growth'



  21. IP Kat Pays the Price for Being a Megaphone of Team UPC

    The typical or the usual suspects speak out about the so-called 'prospects' (with delusions of inevitability) of the Unified Patent Court Agreement, neglecting to account for their own longterm credibility



  22. Links 17/8/2019: Wine 4.14 is Out, Debian Celebrates 26 years

    Links for the day



  23. Nothing Says 'New' Microsoft Like Microsoft Component Firmware Update (More Hardware Lock-in)

    Vicious old Microsoft is still trying to make life very hard for GNU/Linux, especially in the OEM channel/s, but we're somehow supposed to think that "Microsoft loves Linux"



  24. Bill Gates and His Special Relationship With Jeffrey Epstein Still Stirring Speculations

    Love of the "children" has long been a controversial subject for Microsoft; can Bill Gates and his connections to Jeffrey Epstein unearth some unsavoury secrets?



  25. Links 16/8/2019: Kdevops and QEMU 4.1

    Links for the day



  26. The EPO's War on the Convention on the Grant of European Patents 2000 (EPC 2000), Not Just Brexit, Kills the Unitary Patent (UP/UPC) and Dooms Justice

    Team UPC continues to ignore the utter failures that have led to lawlessness at the EPO, attributing the demise of the Unified Patent Court (UPC) to Brexit alone and pretending that it's not even a problem



  27. Links 15/8/2019: GNOME's Birthday, LLVM 9.0 RC2

    Links for the day



  28. 'Foundation' Hype Spreads in China

    Nonprofits seem to have become more of a business loophole than a charitable endeavour; the problem is, this erodes confidence in legitimate Free software and good causes



  29. Links Are Not Endorsements

    If the only alternative is to say nothing and link to nothing, then we have a problem; a lot of people still assume that because someone links to something it therefore implies agreement and consent



  30. The Myth of 'Professionalism'

    Perception of professionalism, a vehicle or a motivation for making Linux more 'corporate-friendly' (i.e. owned by corporations), is a growing threat to Software Freedom inside Linux, as well as freedom of speech and many other things


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts