Bonum Certa Men Certa

Guest Post: Why Not Mono - Part II

In part I, our reader and guest writer was trying to get the underlying ideas about Mono across. There was a car analogy. Here is a more detailed explanation of the picture (metaphorically speaking).






Microsoft is suing someone for not paying Mono rather than paying for Java makes a big difference in the view of the public eye regarding merit and ultimate success. The public understanding of "which side is morally right" would be accompanied for sure by a slew of Microsoft propaganda, that would say: Mono is an intentional direct rewrite of Microsoft IP and enables free rides based on our IP.

It would be hard to convince why Microsoft should not be entitled to collect royalties for such a big chunk of IP, if Novell does pay Microsoft.

“It would be hard to convince why Microsoft should not be entitled to collect royalties for such a big chunk of IP, if Novell does pay Microsoft.”This makes it so much harder for something like Groklaw to counter the propaganda, which is also something Microsoft learned from the SCO-case.

The idea is basically to show that Mono is something like a specially-designed Trojan horse, that masks itself with free-licensing and therefore makes it seem legit and on the same perceived risk-scale than other technologies.

While the original dotnet is genuine (although it borrows and builds on top of a lot of other ideas - just like cars do built on the same old concepts and evolve), Mono is specifically and superficially created, as to incorporate the very same underlying technology - all the blueprints for copying are purposely thrown on the table, and so letting Mono grow fulfills 2 goals:

Goal No. 1



Keep the other numerous car-makers from advancing their technology (which like Java, Python, etc. are also available for free and libre) and therefore prevent the possibility of building useful stuff with other stuff than Microsoft (these are the apps like navigation, car-radios, etc.) Or short: Draining attention away and diverting the landscape so to prepare conquest (divide and conquer). This is done by the license and cannot be debated on why GPL for Java should be good and GPL for Mono should be bad and therefore perceived with more caution.

Goal No. 2



Lure as many developers into building useful apps (or the entire car) with Microsoft-technology.

In my opinion, Microsoft can't do that by developing Mono itself, if it wants to sue for licensing afterwards, because it gets harder to release stuff intentionally UNDER GPL (as opposed to their usual proprietary licenses) and later prove you didn't know what your INTENTION was by pretending to not understood the consequences of the GPL (even v2)...

This is the major point Microsoft learned from the SCO-fiasco, as it was hard to prove that when SCO actively was part of UnitedLinux, it didn't know exactly what it was doing with their "so-called IP" when releasing it under the terms the GPL...

So Microsoft changes and finds the perfect partner to fulfill its goals: Hurt Red Hat as much as possible, and letting Novell only continue develop "Mono" under its protection-racket as to give this project the perception it is legally save for Novell-users. Otherwise, Microsoft would have been forced to stop Novell from developing Mono or start to sue Novell, while with every day passing by, it would have gotten harder to argue that Microsoft stood there so long seeing what Novell was doing (including Mono in Linux), and not to find a "solution" (=cross-patent-licensing) or litigate right away.

Now as Novell is under Microsoft "guided control", Microsoft can much more easily claim that Novell started building something that mimics Microsoft-technology as close as possible in the past, then talked with Microsoft about this (and other) technology resulting in "covenants not to sue" and others distributors or users who want to use Mono too (which resembles dotnet not only from the outside (the look of the apps: the car's shape), but also from the inside (the technology or motor)) should clearly see that Microsoft is entitled to demand royalties from costumers who built their stuff by using a copy of Microsoft-technology to get a "free-ride"...

“Someone has to weigh these arguments in, if s/he choses to defend usage of Mono by claiming it is on the same scale as usage of Java.”It is much, much harder to prove such a case and nurture such a claim for MS with regards to using Java (for example), as MS themselves built dotnet on ideas relating to Java, which could then be proven to be mostly prior art. Java-technology would also get defended by a company like Sun (or Google), and MS had to prove the infringing IP of Java resembling dotnet, which would be easy in case of dotnet vs. mono.

So the litigation-scenario IS a major factor for anyone, who tries to compare the risk of possible litigation on the basis of IP-claims between dotnet and Mono and dotnet and Java. Someone has to weigh these arguments in, if s/he choses to defend usage of Mono by claiming it is on the same scale as usage of Java.

From Microsoft's perspective and the public viewing of such a case, it is clearly not. Even the possible danger from Sun suing over Java is clearly not comparable, because Sun knew what it did when releasing GPL-Java and would have a hard stand to sue anyone not wanting to pay patent-royalties afterwards. If Microsoft would do the same as sun and release an official "Microsoft-certified" dotnet-variant under GPL, later license demanding through litigation would instantly lose a great deal of appeal.

So Microsoft having set up everything in place in its favor with Novell, now sits back and laughs silently as they have found the ONE weak-spot, with they trying to split FLOSS-land: The GPLv2 only and LGPLv2 only, which are poorly designed to such a clever patent-scam-attack. Microsoft weapon is a GPL-tarnished sword called Mono, developed by Novell.

At least, this is how I perceive this whole Microsoft-Novell-nonsense. Now the hard part is to prove this theory other than to wait and let it prove itself. So all we can and should do is make that threat as transparent as possible by exposing its nature to the fullest by just describing it as precisely as possible without making anything up.

Maybe this analogy helps a little to achieve this goal, and raise the awareness to where the difference (and danger) lies.

Mono, ECMA, Microsoft

Comments

Recent Techrights' Posts

Salaries Are Counted in Money, Not in Participation in the Employer's Scheme
articles greatly exaggerating GAFAM salaries
Even Linux Cannot Cope With Slop
Bots on the Web are truly obnoxious
GNU/Linux Has Become More Mainstream in the United Kingdom
It's a long weekend here and we guess some people dabble in GNU/Linux migrations, at least at home
 
Anniversaries Next Month
The month should be otherwise quiet and uneventful for us
Coding is Not Obsolete
we drown ourselves in chaff to meet "LOC" objectives while ignoring everything else
Microsoft Layoffs Perpetual But Silent, People Pushed Out Using Pressure or Incentive Schemes
Earlier this month we named some of the programs
Links 30/08/2026: Apple Rant and LLM (Slop) Scrapers Target Gemini Protocol and Gopher
Links for the day
Walls in Free Software
mind your own business and move on
What a Summer!
Tomorrow is the last day of this month
Links 30/08/2026: Soldiers in Niger Attack Presidential Palace and Airport, Nepali City Struggles to Handle the Many Dead Bodies
Links for the day
Clownflare Sees GNU/Linux Rising to 11% This Past Week
Is it the year of "Linux in China"?
Links 30/08/2026: Russian Strike on a Ukrainian Warehouse and Rhetoric Escalations
Links for the day
Gemini Links 30/08/2026: Photography, Paper Books, Linux Kernel and the Debian Projects Permitting Slop Plagiarism
Links for the day
Imagine a World Where Nobody Fights for Software (and Computing) Freedom
The community keeps fighting back, so some of these ambitions are delayed or watered down
FSF Has Grown (More Staff) After a Year of Financial Growth
On October 4 the FSF turns 41
SLAPP Censorship - Part 166 Out of 200: Garrett Wasn't Found Innocent Per Se, the Court Wanted More Evidence of Who Was Behind Particular Accounts Using Tor
It's complicated
Criminals Don't Obey Laws, California Does Not Enhance Online Safety
It has been a while since we last mentioned so-called 'age-verification' laws
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, August 29, 2026
IRC logs for Saturday, August 29, 2026
Links 29/08/2026: Stop the Hate, Goldfish Myths, and xmpp.nz
Links for the day
Links 29/08/2026: Wave of Social Control Media Bans, Suno Data Breach Class Actions
Links for the day
Links 29/08/2026: Microsoft GitHub Outage (Again), "Displaying Ads Directly on Your Monitor", and "Election Deniers Could Soon Control Elections"
Links for the day
IBM is "Taking the PIP" (Piss), People 'Retire' 'Voluntarily' to "Focus on Family"
IBM has a billion bucks for 'the butcher', but not a million dollars for critical projects and initiatives in Free software
It Should be Uncontroversial to Say That Social Control Media is a Weapon
Democracy is not compatible with the likes of Kapo-Berg and MElon controlling public discourse of billions
Misuse of Bots (Now Sold as "Agents", "Hey Hi", "Automation", and "Efficiency")
They even try to rebrand robotics as "hey hi" and try to sell slop as "work"
Debian: Plagiarism OK, Just be "Responsible" About It
The result isn't the worst, but it's not good either
Don't Let Them Kill Activism
Are the oligarchs shutting the lid on activism and whistleblowers?
SLAPP Censorship - Part 165 Out of 200: Two Years Since My Wife and I Sued
In early September 2024 we hit back
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, August 28, 2026
IRC logs for Friday, August 28, 2026
Gemini Links 29/08/2026: Death Notice, Systems Biology, and Gopher
Links for the day
Links 28/08/2026: Chatbot Pushers Admit They're Used Heavily for Social Engineering Scams, Strong Backlash Against "Smart Glasses" (CCTV on Legs)
Links for the day
Michael Catanzaro's Latest Blog Post Affirms Rumours of Red Hat Changes and RAs/PIPs at IBM
reading between the lines, IBM is "spitting out" Red Hat staff
If Linux Was Written in Rust, 80% or More of Linux Developers Would Not Understand It (Same If It's Composed by LLM Slop)
The licence (GPL) is not enough when there are ways to bypass it
Gemini Links 28/08/2026: Absurd Tomodachi Summer, Screen Piggery, and Jugulans 1.0.3 Released
Links for the day
Links 28/08/2026: "UK Power Grid Has a Phantom Data Center Problem" and "Growth at All Costs is Cancer"
Links for the day
SLAPP Censorship - Part 164 Out of 200: Patent Troll SLAPPs, Defamation Trolls, and Stranglers From America
You start to wonder if the core issue is insecurity
Rumours of More PIPs and Layoffs at Confluent Just Months After IBM Bought It
It is meanwhile apparent IBM will have mass layoffs next week (September)
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, August 27, 2026
IRC logs for Thursday, August 27, 2026
After Many Waves of PIPs (Silent Layoffs) IBM Makes Non-Silent Layoffs, Effective Next Week (September)
What we heard is turning out to be true