Bonum Certa Men Certa

Is Mono's Latest Strategy to Vilify Richard Stallman?

GNU Richard Stallman



Summary: "Move over, Richard, we'll take it from here" -- that's the sort of message embraced by parts of the Mono community

WE already know, based on pretty extensive evidence, that many Mono fans are also close to Microsoft. That is what makes this whole movement rather detrimental to Microsoft's most potent competitor, namely GNU/Linux.



In prior posts about Mono and Microsoft's "Community Promise" (CP) [1, 2, 3] we showed that it had changed virtually nothing. If anything, it finally revealed that Mono has indeed patent traps in it, maybe just not at the core. One of the rudest pro-Mono people (from Debian) is being very blunt about it:

Q: Are there patent issues with Mono?

A: Just like any other software, Mono certainly infringes on thousands of stupid software patents. However the Debian policy with patents is to put them in a trash and pee on them, unless they are actively enforced with reasonable chances to win. The situation of Mono is much more comfortable than (for example) that of MP3 decoders, for which patents are actively enforced; it’s just that they are so lame that we choose to ignore them.

Q: Are there specific dangers coming from Microsoft regarding Mono?

A: Microsoft has claimed to possess patents on some Mono compatibility layers with non-standard Microsoft APIs. Not only this is completely irrelevant to GNOME, since nothing in Gtk# and related stuff uses these compatibility layers, but if you know how things work in the patent world, you already understand this is merely FUD. Microsoft has nothing, but claims to have something in order to scare consumers away from Mono. Actually, not enforcing the patents, while knowing they are violated, would make their case very weak in a patent suit. What their behavior shows is that they are very afraid of Mono. It is stealing customers from their best and most advanced product, their lead development framework. There is absolutely zero chance that they are sustaining Mono from behind, since its very existence is going to make them lose a large amount of money.


He even throws a fit at Stallman at the end. This is part of a pattern for him and other proponents of Mono have been doing the same thing ever since Stallman spoke out regarding Mono [1, 2]. One person even used the F word.

Ubuntu is apathetic towards Richard Stallman's advice [1, 2], but Glyn Moody justifiably distrusts Microsoft on the whole matter. Regarding the CP, he writes:

Now, is it just me, or does Microsoft conspicuously fail to answer its own question? The question was: does it apply to all versions *including* future revision? And Microsoft's answer is about *existing* versions: so doesn't that mean it could simply not apply the promise to a future version? Isn't this the same problem as with the Open Specification Promise? Just asking.


See the comments in GNU/Linux sites to get an impression of how many people reject Mono. It is only a vocal/aggressive minority that seems to be spreading Microsoft inside GNU/Linux, despite opposition from about 3 out of 4 GNU/Linux users (according to a recent poll).

Mono people understand that their attempts to marry Microsoft and Linux are backfiring now that the SFLC and FSF speak out, so Plan B is seemingly to discredit Stallman in person to make his technical assessments go away or be dishonoured. It has gone on for about two weeks. Sam Varghese addresses this issue in a new article where he writes:

Let's remember that De Icaza has gone on the public record stating that he believes .NET is the "natural upgrade" for GNOME. Here's a direct quote: "I'd like to see Gnome applications written in .NET in version 4.0 - no, version 3.0. But Gnome 4.0 should be based on .NET. A lot of people just see .NET as a fantastic upgrade for the development platform from Microsoft."

GNOME 3.0 is around the corner so he probably won't have time to realise his dream. What of version 4.0?

Not unrelated to this whole Mono debate may be the fact that some GNOME people have started a campaign to smear Stallman, to the extent of even releasing a private email exchange. But then is not new behaviour from people at the top of GNOME. Anyone who criticises Mono seems to come in for a rough time.


Jason at the Mono Nono Web site correctly predicted that Stallman would suffer the wrath of Microsoft fans for merely daring to reject Mono. By the way, this is not a reference to one particular person because many blogs independently find an opportunity to pile criticisms on Stallman, for whatever reason or statement that he ever made (there is more than one, but the timing and motive are unlikely to be coincidental).

I told you the knives would come out for Stallman.

[...]

The sad thing is, much of the damage is already done. Stallman is facing a concerted attack on his character and competence and stands little chance of coming through it unscathed. Such is the penalty for daring to critize Mono. This garbage is already all over Planet Gnome, Planet Debian, Monologue and spreading.


The Mono Nono Web site also offers this list of reasons to ignore Microsoft's CP, a clever trick which the 'mainstream' press consistently fell for:

If I had to list my concerns around the Promise I would come up with a slightly different list:

1. Standard bits alone are not enough to deliver killer apps. We have several Microsoft emails about limiting the usefulness of what was standardized, so we know they at least discussed this internally. 2. The Community Promise has that restriction that the Open Specification Promise does not. By not extending the Promise to partial implementations, it could “lock out” alternative implementations of the standard. Limited sub-sets of languages are a common practice in the industry for specialized purposes. 3. The Community Promise will constantly be misrepresented as covering the whole of mono – giving a false veneer of security over the non-covered bits (which end up to be the “juicy parts”) 4. The Community Promise only applies to the current version. This could be used by Microsoft to “freeze out” competing implementations. Just update the standard, but not the promise.



Moreover:

Consider that we know for a fact that F-Spot and Banshee, at least, use non-ECMA covered parts of mono. Maybe they will be re-written soon. That’s great. But at the time of the announcement and currently, they were and are not covered by the standard, and so not covered by the agreement.


And lastly:

There are many such internal documents that clearly show Microsoft understands exactly what standardizing parts of .NET means, and how to keep that offering in control and inferior to .NET. If Mono is not “chasing” .NET, then it fails to meet Windows developers expectations. If Mono is “chasing” .NET, then it both runs the risk of anti-competitive tactics on the non-standard parts, and is undertaking a task not likely to succeed.


Many more answers were delivered regarding Mono (even from Microsoft). Now more than ever it is clear that Mono is a trap and thus it must be avoided.

"I saw that internally inside Microsoft many times when I was told to stay away from supporting Mono in public. They reserve the right to sue"

--Robert Scoble, former Microsoft evangelist

Comments

Recent Techrights' Posts

Intimidation, Threats, and Bullying Not Tolerated by Techrights
When it comes to our reporting, safety always comes first
Something to Celebrate in Gemini Protocol
More capsules and users join in
 
Banned evidence: Ars Technica forums censored email predicting DebConf23 death, Abraham Raji & Debian cover-up
Reprinted with permission from Daniel Pocock
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, March 28, 2025
IRC logs for Friday, March 28, 2025
A World Without Rules
We're long insisted on better laws and actual enforcement of them (applicable to all, not selectively applied)
IBM's BS (Bait, Switch) Regarding Ways to Stay Onboard
PIPs, RTOs, and forced relocations are just an illusion of choice (or ability to recover)
statCounter Sees Microsoft Windows Falling to New, Unprecedented Lows in Palau
Taking Android into account, Windows is now down to an all-time low of 14%
Google News Lost the Fight to LLM Slop (While Google Itself Sells Slop, Nowadays Under the Name "Gemini")
Many people say that "Google is getting worse"; that's almost an understatement
Links 28/03/2025: AirAsia Trouble Again, UMich Culls All DEI Programs
Links for the day
Gemini Links 28/03/2025: Alexa is for Gullible People, Rant About Feature Overload
Links for the day
The SLAPPs From the Microsoft Strangler (and Sidekick) No Better Than Patent Trolling
one must never settle with trolls
Links 28/03/2025: Last Reminder "to Delete Your 23andMe Data", "UK's First Permanent Facial Recognition Cameras Installed"
Links for the day
Microsoft Canonical Continues Its FUD (Fear, Uncertainty, Doubt) Campaign, Reveals Google Too Sponsored It
They're paid-for lies from a Chinese company that takes GAFAM money to write puff pieces about them
Android Rises Above 76% in Mozambique, Leaving Windows in the Dust
Windows may soon be measured as smaller than Apple's iOS
IBM, Red Hat and Microsoft Probably Also Manipulate Metrics (It Helps Con the Shareholders)
Wall Street's credibility will depend on enforcement of "checks and balances"
Slopwatch: trendhunter.com and Other Pure Junk From "Google News"
The need to vet sources is hardly new; anyone can spew out anything, anywhere. There's a need for vetting.
Gemini Links 28/03/2025: Rewatching The X-Files, Slop Concerns, and NOSTR Censorship
Links for the day
Links 28/03/2025: Australia at Risk, EPO Grants Illegal Patents With Illegal Effect
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, March 27, 2025
IRC logs for Thursday, March 27, 2025
Links 27/03/2025: Obituary to a Shop, Russia Trying to Buy Time
Links for the day
Links 27/03/2025: Slop, Autosuggestions, and Nostr
Links for the day
Apparently Confirmed: IBM Layoffs in Canada Today, Hundreds Affected
Impacting "177 people", says one person, "in Ottawa"
When Windows Was Dominant (1990s) Browser Monopoly Meant MSIE, But Now Google Android is Dominant and the Web in a 'Webapps' Era Works With (or Is Designed for) Chrome-isms
We've been there before
Slopwatch: BetaNews, LinuxSecurity.com, and the Attack on Web Search Using Fake and Likely Plagiarised Pages
Changing a few words here and there won't change the fact that it's not properly authored
Links 27/03/2025: U.S. Honeybee Deaths Reach Record High, Legal Occupation Next in Line After War on Science
Links for the day
Using Courts for 'Revenge' is Always a Losing Strategy
Trying to cause someone you dislike to spend a lot of money
IBM CFO James Kavanaugh Refers to Firing of Almost 10,000 Americans as "Workforce Rebalancing" (Shifting IBM's Centre of Balance to Low-salary Contracts/Countries)
The scale of IBM layoffs is getting too large to evade WARN Notices
[Video] Dr. Richard Stallman's Keynote Speech in Kerala Finally Uploaded
In non-free format and proprietary YouTube, but perhaps that's better than nothing
Islands Are Leaving Microsoft Behind, According to statCounter
Android has had a very strong year
EPO Management Fails to Deny That the Office is Discriminating Against Women
Europe's second-largest institution isn't just exceedingly corrupt but also immoral
In Some Countries the Market Share of Vista 11 is Going Down, Not Up
despite being released in 2021
Rumour: Mass Layoffs in IBM Canada Today
Maybe later today some people from Canada will say something firmer and maybe some media will even talk about that
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, March 26, 2025
IRC logs for Wednesday, March 26, 2025
Gemini Links 27/03/2025: X-Files' "Kill Switch", Orlando, and ASN (Autonomous System Number) 'Hack'
Links for the day