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

SLAPP Censorship - Part 194 Out of 200: The Court Needs to Also Look Into Microsoft-Controlled Restricted Boot Advanced by An American (Garrett) to Promote Monopoly and Back Doors Everywhere
Kill switch sold as 'security' is like euthanasia sold as a cure
Linux Kernel Becoming a Slopfest - Part 7 - Infested With or Plagued by Bot-Generated Slop, Committed by Microsofters
Slop is a security threat; even the person committing slop to Linux might not be aware that there's a back/bug door in the code
Edward Snowden Lost His Voice, Then His Leaks Lost Exposure (Access Denied)
When states want to deny people access to some information they have many tools at hand
 
SLAPP Censorship - Part 195 Out of 200: Two Years Since Garrett, Graveley and Lozza Worked in Parallel to Censor Techrights
It began in September 2024, shortly after we had sued Garrett
Linux Kernel Becoming a Slopfest - Part 8 - In Conclusion
this can invite more SCO-like problems in the future
Germany, Like Switzerland, Will Dump Microsoft's Proprietary Software and Disservices, Then Dump Windows for GNU/Linux
This impacts not only the Windows revenue; this corrodes any "rents" Microsoft was getting from "subscriptions"
Microsoft Shuts Down More Studios, Morale Low, More Mass Layoffs Ahead of Reports
They pretend it's not happening or that it's a lot smaller than it actually is
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, September 22, 2026
IRC logs for Tuesday, September 22, 2026
Gemini Links 23/09/2026: Ljubljana, Poetry, and FORTRAN
Links for the day
The EPO's Central Staff Committee (CSC) Shows Job Insecurity at Europe's Second-Largest Institution
Who would want to join a company with such low job security?
There Are Thousands More Microsoft Layoffs (Including Silent Layoffs), Not Hundreds
Microsoft does have layoffs and today is no exception (except Microsoft talks about it)
Gemini Links 22/09/2026: Disability Studies, Slop Boosters, and TkInter
Links for the day
Links 22/09/2026: Flock is Collapsing Amid Mass Backlash and Internet Society Collaborates With the 'Epstein Class' (Trafficking of Women)
Links for the day
Raspberry Pi Has Microsoft Secrets Inside, Now DRM
now we deal with SBCs that have DRM in them, put there for commercial reasons
2 Hours Ago The Register MS Published a Page That Says "AI" 42 Times Because It Was Paid to Do So
Still inflating the bubble for money
Gemini Links 22/09/2026: Scout Night, Cybernetic Capitalism, and Thoughts on Companies Forcing People to Adopt Plagiarism Engines
Links for the day
Links 22/09/2026: "An Arsenal of Surveillance" and Slop Bots Suggest Starting Wars
Links for the day
SLAPP Censorship - Part 193 Out of 200: Breaks GNU and Linux, Tries to Silence Critics, Loses All Money, Looks for Microsoft Allies and Sponsors
The latest emotional knee-jerk reactions serve to confirm what we have long said
Things Will Only Get Better (as We Go Backwards)
It only gets better. If you go back in time.
UK High Court Shows SRA is Totally Useless in Curbing SLAPPs, This Has Impact on Our Reporting on the SRA Next Week
We'll carry on our coverage and soon finish the current series that so we can get on with more time-sensitive ones
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, September 21, 2026
IRC logs for Monday, September 21, 2026
Links 21/09/2026: "Lies of the Hey Hi (AI) Industry" and Solar Power Is Getting Cheap
Links for the day
Gemini Links 21/09/2026: Equinox and Beginner's Guide to Gemini
Links for the day
Links 21/09/2026: "Back On My Bicycle" and American Regime's War on Media Escalates Further
Links for the day
SLAPP Censorship - Part 192 Out of 200: The Hired Guns of Garrett and Graveley Sent Us USB Sticks (One to Me, One to My Wife) Showing Lozza Talking to Garrett About Censoring/Deplatforming Techrights the Same Time Graveley Was Copy-Pasting Garrett's Lawsuit
Next year we plan to bring this matter to the Court of Appeal
Linux Kernel Becoming a Slopfest - Part 6 - Seeing Who Contaminates Linux With Slop (And Also Admits It)
Today we begin looking at some culprits
2026: The Year Galleries Realised the Need to Flag or Cull Slop Images
Society needs to shun slopfarms, people who use LLM slop (for anything at all), companies that use bots (which they dub "agents"), and so-called 'coders' who volley garbage into project and software hubs
Software Freedom Day Celebrated in 5 or 6 Continent
Software Freedom Day (SFD) 2026 was big this year
SLAPP Censorship - Part 191 Out of 200: Garrett, Graveley and Lozza
They talk to and coordinate with one another
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, September 20, 2026
IRC logs for Sunday, September 20, 2026
Gemini Links 21/09/2026: Digital Hoarder, GTD, Minimalism vs Digital Minimalism, Rejection of LLMs
Links for the day