09.19.08

Guest Post: Why Not Mono – Part I

Posted in Microsoft, Mono, Novell at 8:01 am by Dr. Roy Schestowitz

Those who work at Novell and also sympathise with Microsoft sometimes say so. Those who work at Novell and dislike Microsoft (or Windows) would put their job at risk by criticising Novell’s big partner and new source of revenue. The same goes for .NET — and by association Mono — so we expect no public outburst or resentment towards this direction coming from inside Novell.

It is important to understand why Mono is dangerous. Mono is Novell and Novell is growing closer and closer to Microsoft as time goes by. As a reader points out, “we really don’t know, what is happening behind closed doors, but there is nothing good to be expected.”

The same reader has prepared a short document, which he thought might be useful for people as they try to give a clearer picture why exactly it is different comparing DotNET vs. Mono than DotNET vs any other technology.

“Like the Google comic, sometimes a picture says more than words and sticks in the minds better,” he wrote. So here goes:


Why .NET to Mono related to Patents is a different thing than e.g. .Net and Python…

Mono car analogy

DotNet gets you there, like doing a simple mathematical operation like 1+1 = 2 Mono does it in the same way, emulating DotNET as closely as possible. So MS could argue that Mono does not only resemble its “original” a great deal, It basically incorporates the same internals.

Let’s say that DotNET has a diesel as motor, so does Mono.

“Demanding royalties on so-called IP, knowing its competitor uses a derived model with the same internals to make it “tick”.”Generally, every car uses a some kind of motor. But it would be very much more likely to be successful to sue for a company. Demanding royalties on so-called IP, knowing its competitor uses a derived model with the same internals to make it “tick”.

E.g. if DotNet uses a special hybrid-motor, it would be more likely for MS to make its case in the public opinion (which is crucial for the moral acceptance if MS decides to sue) sound “legit”, than if it would try to sue “Python”, which also uses the “4-wheel-technology”, has a motor and brings you from a to b (e.g. also arrives at the conclusion that 1+1 = 2), but ultimately shares this with any vehicle and would make it much harder for MS to attack while not being viewed as an “SCO-like”-attack.

Then the risk of Python itself (as the inventor of the Python-model) suing other “car-makers” based on their Python-technology is infinitely smaller compared due to its open-source-nature as opposed to MS as the DotNET-car-maker regarding its Mono-Clone…

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

This post is also available in Gemini over at:

gemini://gemini.techrights.org/2008/09/19/why-not-mono-car-analogy/

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

11 Comments

  1. aeshna23 said,

    September 19, 2008 at 8:26 am

    Gravatar

    I don’t like the illustration at all! DotNet and Mono are represented by antique cars, but Python is represented by a child’s toy. While I hate the internal combustion engine, the message I get from the illustration is Python is a toy and DotNet and Mono are real tools.

    How using a propeller plane for Python?

  2. Roy Schestowitz said,

    September 19, 2008 at 8:31 am

    Gravatar

    Yes, well, I didn’t make the illustration.

  3. AlexH said,

    September 19, 2008 at 8:38 am

    Gravatar

    Amusing that the illustration was chosen to probably give the opposite impression (old car versus race car).

    I don’t think this article particularly makes the case Mono and DotNet are similar internally; that seems to be a pretty big assumption.

  4. Dan O'Brian said,

    September 19, 2008 at 8:59 am

    Gravatar

    I was pretty disappointed in this article – yesterday you claimed someone had done “in-depth research” on Mono and that you would post it today. I can only presume you meant this… but I don’t see any “in depth” research at all. This article is severely lacking in any sort of research at all.

  5. mike said,

    September 19, 2008 at 6:00 pm

    Gravatar

    “(e.g. also arrives at the conclusion that 1+2 = 2),”

    teehee … about what I personally think of Python ;-)

    Not a very good argument in this article, simplified to the point of not being meaningful at all.

    Particularly since both are software, and the only `engine’ they both use is the same (modern at that) cpu.

  6. Jose_X said,

    September 19, 2008 at 8:11 pm

    Gravatar

    >> I don’t think this article particularly makes the case Mono and DotNet are similar internally; that seems to be a pretty big assumption.

    Don’t they follow the same set of specs, more or less? No one claimed the cars were built by the same people. The point is that they have the same internal interfaces. There may be variations in the parts but the interfacing sections and tolerances must match in many cases. This is land open to patent grabs.

    And what about when you find that the MSdotnet car doesn’t follow the spec quite right or adds something, then mono has to follow (as per their marching orders in order to “maintain” interop). These deviations from the blueprints aren’t covered in any Covenant I don’t think.

    >> Particularly since both are software, and the only ‘engine’ they both use is the same (modern at that) cpu.

    In the analogy, every part of the car (all material hardware) is likened to software. The actual car components are like the dotnet software component implementations. Each car follows the same set of blueprints. This corresponds to the MSdotnet and mono following the same interface specs. The implementation designs could be similar in various areas but might not be. Designs will tend to be similar a lot more often if the interfaces being followed are the same. I think both the designs and the interfaces can end up in patents.

    I think the patent grabs are overstepping constitutional boundaries and have other problems. I don’t pay too much attention to the subtleties of patents and patent law, so I don’t want to go further.

  7. Roy Schestowitz said,

    September 19, 2008 at 8:29 pm

    Gravatar

    AlexH, there’s more explanation about this coming tomorrow.

  8. AlexH said,

    September 20, 2008 at 3:39 am

    Gravatar

    @Jose:

    Don’t they follow the same set of specs, more or less?

    To be clear, they process the same format data. But saying that means they work internally the same is a big stretch: gcc and LLVM, for example, compile the same code to the same object format. Internally, they work entirely differently.

    As I said before, Mono itself has a JIT runtime and a non-JIT runtime: those two systems alone work entirely differently.

  9. Balzac said,

    September 22, 2008 at 10:12 am

    Gravatar

    I agree with the writing but M$ products should be represented by an ugly car. Maybe an Edsel would be more appropriate.

  10. Roy Schestowitz said,

    September 22, 2008 at 10:28 am

    Gravatar

    I’ll definitely do that if I produce an image in the future. This picture is not mine however.

  11. Jose_X said,

    November 23, 2008 at 9:22 pm

    Gravatar

    >> To be clear, they process the same format data. But saying that means they work internally the same is a big stretch: gcc and LLVM, for example, compile the same code to the same object format. Internally, they work entirely differently.

    From what I know about Java, there are many interfaces which depend on other interfaces very precisely (the spec is not perfect in separating implementation from standard so my memory might be mixing the two some). Also, I’m talking about the whole stack.

    Even if you were only talking about some core component equivalent to a JVM, I think that can include many many structural aspects that many people would not think twice about patenting around.

    There is Bilski, so we shall see.

What Else is New


  1. Links 18/6/2021: Mir 2.4, ActivityWatch 0.11, Microsoft Breaks Its Own Repos

    Links for the day



  2. [Meme] When the 'Court' Drops

    As the EPO sneakily outsourced courts to American companies and parties in dispute depend on their ISP for “access to justice” there’s a catastrophic impact on the very concept of justice or the right to be heard (sometimes you don’t hear anything and/or cannot be heard)



  3. The EPO's Virtual Injustice and Virtual ('News') Media

    A discussion of this morning's post (part 10 in a series) about the shallow media/blog coverage that followed or accompanied last month's notorious EPO hearing



  4. Links 18/6/2021: LibreOffice 7.2 Beta, Elementary OS 6.0 Beta 2, and Linux Mint 20.2 “Uma” Beta

    Links for the day



  5. The Self-Hosting Song

    Cautionary tales about outsourcing one's systems to companies that could not care less about anyone but themselves



  6. IRC Proceedings: Thursday, June 17, 2021

    IRC logs for Thursday, June 17, 2021



  7. [Meme] Swedish Justice

    The EPO‘s patent tribunals have been mostly symbolic under the Benoît Battistelli and António Campinos regimes; giving them back their autonomy (and removing those who help Battistelli and Campinos attack their autonomy) is the only way to go now



  8. Virtual Injustice -- Part 10: Vapid and Superficial Coverage in the 'IP' Blogosphere

    The media has come under attack by Benoît Battistelli; during the term of António Campinos most of the media critical of the EPO has mostly vanished already; so one needs to look carefully at comments and social control media



  9. Links 18/6/2021: RasPad 3 and Pushing Rust Into the Linux Kernel

    Links for the day



  10. Heli Pihlajamaa Promoting Software Patents to Patent Maximalists

    "Ms Pyjamas" from the EPO is promoting illegal software patents to a bunch of patent zealots (CIPA)



  11. The Lying by Team UPC, Led Again by Kevin Mooney

    Team UPC, or specifically Mr. Mooney, lies to the public about the prospects of the UPC; similarly, EPO and EU officials keep bringing up false claims about the UPC, so while the UPC itself has likely died for good the lies have not



  12. Links 17/6/2021: Cutelyst 3 and Lenovo Move Towards ThinkPad BIOS Configuration From Within Linux

    Links for the day



  13. Too Much Noise and/or Distraction and General Loss of Focus (on the Real and Urgent Issues, Such as the Ongoing Anti-FSF 'Coup')

    The media is full of Microsoft fluff and technical blog posts still focus on the Freenode fiasco, among other things that don't matter all that much; but we certainly need to talk about steps undertaken to undermine the FSF's power because long-term ramifications may be huge



  14. [Meme] The Enlarged Bored People With Presidential Decrees

    The laughable state of the EPO‘s EBA (or EBoA) is rarely commented on anymore, not even in so-called ‘IP’ blogs; maybe they’re just so eager to see patents on everything, even European software patents, so tyrants who destroy the courts (with UPC lobbying and removal of EBA independence) don’t bother them so much anymore



  15. Response to Misinformation From EPO Officials

    Opponents of European software patents are clearly being mischaracterised by EPO officials, who also use meaningless buzzwords to promote such patents; as an aside or footnote that relates to our ongoing series we’re making this quick video, which is days late



  16. [Meme] Tilting the Scales for Software Patents

    Shovelling up lots of patents, even worthless patents such as software patents, dooms the EPO (EPC violations, lawlessness), dooms European professionals, but the wrong people have been put in charge and courts are being intimidated by them



  17. Virtual Injustice -- Part 9: Heli, the EPO's Nordic Ice-Queen

    Team Campinos is full of people who instead of grasping and working to promote innovation are boosting the agenda of litigation (scientists are not being employed)



  18. IRC Proceedings: Wednesday, June 16, 2021

    IRC logs for Wednesday, June 16, 2021



  19. Links 17/6/2021: elementary OS 6 Beta 2 and JingPad Linux Tablet Crowdfunding

    Links for the day



  20. Techrights Statement on IRC

    Freenode needs to explain what the hell happened this week and why communities that make up the network weren't informed or consulted



  21. IRC Proceedings: Tuesday, June 15, 2021

    IRC logs for Tuesday, June 15, 2021



  22. Virtual Injustice -- Part 8: A Well-Connected 'IP' Maximalist

    The EPO‘s lobbying for European software patents goes all the way to the top, including António Campinos and his circle



  23. Links 16/6/2021: Alpine 3.14.0 and DXVK 1.9

    Links for the day



  24. Links 15/6/2021: Debian Installer Bullseye RC 2 and Zink Updates

    Links for the day



  25. IRC Proceedings: Monday, June 14, 2021

    IRC logs for Monday, June 14, 2021



  26. Virtual Injustice -- Part 7: Musical Chairs and Revolving Doors

    Cross pollination in Alicante and Munich serves to show that people aren't picked for their skills and experience; it's like a private club or a clique



  27. Hardly Shocking and Not At All Surprising That Thugs Who Run the EPO Hired External Thugs to Help Them Oppress Aggrieved Staff

    With the EPO's management flooding the bank accounts of aggressive law firms (at our expense) we need to ask serious questions about how such a "Mafia" (what EPO staff calls the management) managed to metastasise inside Europe's second-largest institution and how to remove this "Mafia" as soon as possible (some arrests too are well overdue)



  28. [Meme] There Are No Elections in Mafia-Type Regimes; It's About Family and Friends...

    With no real concept or notion of "elections" (the so-called 'mafia' members choose their successors and colleagues) the EPO's patent examiners clearly need outside intervention, e.g. inquest by the EU authorities (the EPC died and maybe the EPO too; it's unregulated and it grants false patents that harm Europe because the courts don't function, either)



  29. Today's Linux Standing for the Opposite of What Linux Users Stand for

    The so-called 'Linux' Foundation or the "Corporate Linux Foundation" is alienating many of the original users of GNU/Linux and it still insults their intelligence; it's rewriting history, it still distorts the objectives, and before we know Linux will perish and lose momentum because all the excitement associated with the brand will fizzle away



  30. Links 14/6/2021: Kdenlive 21.04.2 and Raspberry Pi 400 Support in Linux

    Links for the day


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts