Bonum Certa Men Certa

Reader's Article: Microsoft's Empty "Community Promise" (Mono) is a Sham

Mono, ECMA, Microsoft



...or How I Learned to Stop Worrying and Look at the Wookie.

Misdirection is a curious thing, and in the hands of Microsoft "evangelists" (such as Miguel de Icaza), it's positively dangerous.



Apparently, de Icaza is slavering [1] over Microsoft's recent announcement [2] that they "will be applying the Community Promise [3] to the ECMA 334 and ECMA 335 specs".

That's nice.

So now the pro-MONOpolists have three things to cheer about:

1. Poisoning Free Software with Microsoft's IP (and paradigm) 2. The ECMA RAND /price/ guarantee 3. Microsoft's misleading "covenant"

Let's look at these in more detail.

First, if we naively assume there are in fact zero "IP" risks involved in implementing C#/CLI, that still leaves the question of why should the Free Software community help spread Microsoft's standards, regardless of how "safe" any of those standards might be?

After all, Microsoft is the self-declared enemy of Free Software, they think it's "a cancer", and that GNU/Linux is "Microsoft's number one competitor". Their criminal and unethical behaviour alone, over the last three decades, should be sufficient reason to not want to help them, but given the very obvious conflicts of interest here, I'd say it's patently obvious there must be a catch. Microsoft is not the sort of company that helps its competitors ... ever, not unless it can work some nefarious angle (embrace, extend, and extinguish).

Historically, and still to this day (OOXML), Microsoft uses its proprietary, reinvented "standards" to try to squash all competition, by tying those "standards" to software that's bundled with nearly all PCs, by OEMs, under financial coercion [4] [5].

Bear in mind that this devious "standards" tactic is the key weapon Microsoft uses to protect its monopoly.

Is this something we should be helping them with?

“Microsoft is not the sort of company that helps its competitors ... ever, not unless it can work some nefarious angle (embrace, extend, and extinguish).”The second point, and I'll make it brief since there's very little to discuss about it, is that the ECMA RAND is only a guarantee of fair price (parity). It has nothing whatsoever to do with Microsoft's rights to sue you for patent violation. A classic misdirection used by the pro-MONOpolists.

The final, and most pertinent point, is that Microsoft's so-called "Community Promise" is just another misdirection, because its "truths" are incomplete, in some cases questionable, and in yet other cases wholly irrelevant (essentially non sequitur).

Here's a simple analysis:

The "covenant" (and the RAND) do not apply to large portions of .NET (e.g. ASP.NET, ADO.NET and Winforms). This is significant because it means .NET programs which utilise these components will not be (legally) interoperable with systems running Mono. This means there will be great disparity between C# programs on Windows and their ports on GNU/Linux, and this fact will be abused by Microsoft to promote Windows as the "better" system. It will also have the effect of attracting Mono developers over to Windows, who may subsequently abandon GNU/Linux. It may even represent an actual "IP" risk, if de Icaza and friends are not entirely vigilant (or possibly if they're complicit with Microsoft's anti-Free Software agenda. At this point, anything's possible).

The "covenant" conveniently ignores these essential details.

Microsoft also makes a big deal out of its claim that this "covenant" is "legally binding". Well, is it? Not really. It's not legally binding in the sense that an actual patent grant is, since that is an explicit contract with a named party. It may become legally binding ... if used as a challenge in court. But of course it does actually need to be tested in court /first/. If you were, for example, Red Hat, would you want to be the guinea pig? Oh how Microsoft would love the opportunity to squash that piggy.

In fact, it's debatable whether they'd even be covered by this "covenant" at all, since (in Microsoft's own words) "The CP applies only if the implementation conforms fully to required portions of the specification. Partial implementations are not covered" ... and "The Community Promise applies to all existing versions of the specifications". So this raises the questions what is covered, and exactly how feasible is it to implement this "full specification" under Mono (or DotGNU, or any other unlicensed implementation)? Even more importantly, what will not be covered in the future, as and when the specifications change?

Oh yes, Microsoft also make a big deal about their claim that these rights are "irrevocable", but they fail to clarify that these "irrevocable rights" only apply to the standard as it stands today. And we all know how Microsoft loves to "extend" things, don't we?

So in summary, Microsoft's "promise" is worthless, irrelevant, and entirely misleading. I'm sure it'll bring a brief moment of euphoria to the pro-MONOpolists, who will now believe they have a new argument to support their aspirations to poison Free Software with Microsoft's toxin, but in the long term it amounts to nothing. Nothing but trouble, at least. ____ [1] http://tirania.org/blog/archive/2009/Jul-06.html [2] http://port25.technet.com/archive/2009/07/06/the... [3] http://www.microsoft.com/interop/cp/default.mspx [4] http://www.groklaw.net/article.php?story=200... [5] http://www.birdhouse.org/beos/byte/30-boot...

Analysis by Slated



"The shepherd drives the wolf from the sheep's throat, for which the sheep thanks the shepherd as his liberator, while the wolf denounces him for the same act, as the destroyer of liberty. Plainly the sheep and the wolf are not agreed upon a definition of the word liberty; and precisely the same difference prevails today among human creatures." ~ Abraham Lincoln

Comments

Recent Techrights' Posts

Video: University in Peru Honours Richard Stallman
Tomorrow, January 20, Richard Stallman speaks in France
January 20: Richard Stallman Talk in Europe
evening time in Europe, around midday in the United States and Canada
 
FOSDEM is Called "FOSDEM" Because of Richard Stallman (RMS)
The overlap there seems timely; yesterday RMS spoke in French-speaking (in part) Switzerland where questions in French were accepted
Links 19/01/2025: TikTok (Fentanylware) Now Banned in the US, Convicted Felon Talks to Fentanylware CEO and Pooh-Tin About Undoing the Ban Despite the Supreme Court Unanimously Upholding It
Links for the day
FTC Realises Microsoft Buying Fake 'Clients' to Fake "Revenue" (Microsoft 'Buying' Services and Products From Itself!)
Ponzi scheme
Total Lock-down Ambitions - Part III - The Web Browser as DRM Pusher
A lot of "streaming" stuff is DRM
IBM Termination Story and Information From Microsoft About Mass Layoffs
In 2 weeks of 2025 Microsoft already had 2 waves of layoffs
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, January 18, 2025
IRC logs for Saturday, January 18, 2025
Links 18/01/2025: Restoring the Great Wall of China and Economic Expansion in China
Links for the day
Guardian Digital (linuxsecurity.com) is Spamming the Web With Microsoft's Promotional LLM Slop About UEFI 'Secure' Boot (Which is Against Real Security)
This is an attack on honest journalism
Links 18/01/2025: TikTok's Endgame, "Car Freedom", and Spying in Cars 'Fines' GM (Settlement)
Links for the day
Links 18/01/2025: Apple Getting Out of Hey Hi (AI) Slop (Too Much Misinformation), Chaffbots/Chatbots Try to Settle Copyright Infringement Lawsuits
Links for the day
What Fake News Sites Are Doing to GNU/Linux
The LLM slop about Linux serves two purposes
Links 18/01/2025: Microsofters Upset at Microsoft's Ridiculous Rebrands (Excuse for Massive Price Hikes), Chaffbot Company ('Open'AI) Faces More Lawsuits
Links for the day
Gemini Links 18/01/2025: Surge in Illnesses, ctags, and Gemsync
Links for the day
Slopwatch: Too Lazy to Write Real Articles, Offloading to Chatbots Instead (LLM Slop About "Linux")
The Web was already full of garbage before the LLM frenzy. Now it's even worse.
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, January 17, 2025
IRC logs for Friday, January 17, 2025
RMS 'Inauguration' in Montpellier (Government Administration) on January 20th
Happy hacking
Even Technical Articles and HowTos From UNIXMen Nowadays Seem to be LLM Slop
We've just permanently removed the RSS feed of UNIXMen
The FSF's 2024 End-of-Year Fundraiser Succeeds: Over $400k to Support Software Freedom
That's worth bringing up again because the SFC is trying to 'crash' this achievement of the FSF
[Meme] Fentanylware (TikTok) Banned in the United States, Next Up European Union (EU)
And the United Kingdom (UK)
President Biden is Right, "Free Press is Crumbling" and the United States Exports Its Media-Hostile Culture to Other Continents
perhaps Biden should pay closer attention to how Donald Trump-inspired Americans take their battles to other continents
Links 17/01/2025: TikTok Banned by the United Stated (SCOTUS Rejects Appeal)
Links for the day
Software Freedom Conservancy Inc (SFC) Makes It Obvious It's Just a Copycat Trying to Exploit or Leech Off the FSF's (and GNU's) Work
They swim next to the rich people (who "match")
Links 17/01/2025: Fentanylware (TikTok) Herds Its (Drug) Users Into Even More Harmful "Apps"
Links for the day
Guardian Digital, Inc (linuxsecurity.com) Uses Microsoft-Controlled Front Groups and LLM Slop in Order to Spread Microsoft-Directed Anti-Linux FUD
Microsoft garbage likely produced by Microsoft LLMs, spewing out Microsoft FUD
Likely Fake 'Article' About Linux Mint 22.1
BetaNews fired up its plagiarism machine (LLM)
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, January 16, 2025
IRC logs for Thursday, January 16, 2025