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

Snooping EPO Management, Sniffing Up Every Staff Action
It this a problem for whistleblowers? Of course.
Don't Do That
Options do exist. People should exercise freedom.
Iran Has Debunked GAFAM and Cloud Computing as Safety of Data
Cloud of smoke?
SLAPP Censorship - Part 188 Out of 200: Used, Then Discarded, by Microsoft (as We Predicted All Along, It's Always Like That)
The longer they carry on with it, the more scandalous this will get
 
Slop Ruins Development and Reverse Engineering, It Rewards Retarded "Slop Kiddies" (to Quote Andy ‘TheFlow0’ Nguyen)
Slop is just a fatal cancer that kills the body, then dies with the body it killed
Internet Relay Chat (IRC) and Mailing Lists Are Still Better Than Discord, Slack, and Discourse
Discourse is "open" "bossware"
Links 18/09/2026: Disgust Over LLMs and Why "Agents" (Bots) Are Nothing More Than "Spam"
Links for the day
Software Freedom Day is Tomorrow
events coming
Illegal and Unconstitutional Tribunal That SLAPPs Critics Does the Illegal and Unconstitutional: It "Rubberstamps Software Patents"
This is not a legal system. This is mafia.
Privilege in 'Linux' Foundation (Double Standards) and What the FSF Should Avoid Doing
If RMS can talk about politics, others too should be able to talk about politics
Seems Like Many Microsoft Layoffs Are Going On Right Now (Forever Layoffs)
Like IBM, Microsoft hopes shareholders will not know of morale and financial problems
More Threats From the Person of Restricted Boot Infamy
Remember this is the man who is the principal purveyor of restricted boot and who landed restricted boot in Linux
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, September 17, 2026
IRC logs for Thursday, September 17, 2026
Linux Kernel Becoming a Slopfest - Part 3 - Besieged by LLM Bots, Now Hiding Behind a Wall of JavaScript
The series began 3 days ago
Gemini Links 18/09/2026: Modern Linguistic, Boxing, Turning 40, and Solar MiniServer
Links for the day
Links 17/09/2026: Studio Closures and Negative Rumours About Microsoft XBox Again
Links for the day
What's Wrong with Microsoft's GitHub, New Article by Jacob Bachmeyer and Richard Stallman
licensed under a Creative Commons Attribution-NoDerivatives 4.0 International License
EBay is Going to Die Soon
Users will flee
Red Hat PIPs. The Only Question is, How Many?
Insiders know what's coming soon
This Week The Register MS Published a Page With "AI" 34 Times in It and It Was, as Usual, Paid SPAM!
Does The Register MS understand that it is doing harm to its audience (for temporary gains)?
43rd Anniversary of the GNU Project Announcement
Coming soon
General Assembly (Meeting of All Staff) Starts in Hour Ago to Discuss Strikes at Europe's Second-Largest Institution (EPO), Strikes to Last Until End of 2026 (If Not Further)
The media absolutely does not cover this and that's intentional
SLAPP Censorship - Part 187 Out of 200: Reminding Ourselves of the Great Damage Garrett Did to Linux (for Microsoft)
he rejects freedom
Cancel Culture is a Cancer That Harms Democracy, Justice, and Science. It's Designed to Help Corporations Vanish Their Critics.
"Codes of Conduct" sounds benign; in practice, however, it is not
Links 17/09/2026: Class Action Lawsuit Over GAFAM's "NameTag" and Automattic Hides What It Did to CEO Mullenweg (or Why)
Links for the day
Gemini Links 17/09/2026: Google Signals the End, ROOPHLOCH Coverage, EBay Uses Offensive Bots to Falsely Accuse Users of Stuff
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, September 16, 2026
IRC logs for Wednesday, September 16, 2026
IBM's Anderon Another Opportunity for Debt-Loading, Publicity Stunts, Maybe Hidden Layoffs
Anderon is like Theranos
In Praise of 7 Years of Alex Oliva in the FSF, Not IBM
Thank you, Mr. Oliva, for 7 years of uncompressing advocacy and perseverance
SLAPP Censorship - Part 186 Out of 200: Love (Always Commands)
This coming Friday we celebrate our wedding anniversary
With Half of September Finished Clownflare Radar Sees GNU/Linux at 7% "Market Share"
On desktops/laptops
Linux Kernel Becoming a Slopfest - Part 2 - Bribes From Slop Pushers Divide Us
Money can and does divide people
Gemini Links 16/09/2026: Cards, Nature, and Conspiracy Theorists
Links for the day
Links 16/09/2026: Proprietary Chatbots Company Lets Humans Moderate Chatbots, "Putin Looking to See How Far he Can Push NATO"
Links for the day
The Only Still-Supported Version of Windows Breaks Itself (Again), the Microsoft Layoffs Will Carry on in Secret
In the US they marked about 7% for removal just this past summer
Wikileaks Turns 20 Just 18 Days From Now
it's fair to say they've endured online, but aren't lively/active
The Cyber Show Debunks the Alleged Intelligence in Slop
It's shorter than usual
Expecting Failure
Some things would not happen to technology (tech) experts because they know how things work and what to expect (or watch out for)
Links 16/09/2026: US Running Low/Out of Some Ammo Due to Wars, Slop Bots "Are Using an Outrageous Amount of Electricity"
Links for the day
"AI Slowdown" is Code Word for Bubble Imploding (Trying to Make This Slowdown Seem Wilful, an Act of Safety and Responsibility)
They help one another by inflating the bubble and making false excuses when expansion stalls
SLAPP Censorship - Part 185 Out of 200: What Reputation?
Helping monopolies and working for monopolies never made anybody popular
Gemini Links 16/09/2026: Slovenia, Catastrophe Ethics, and ROOPHLOCH 2026
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, September 15, 2026
IRC logs for Tuesday, September 15, 2026