EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

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 this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

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. Recharging for 2020

    Techrights prepares for another big year with more coverage than past years (we have become more efficient and our team grows)



  2. Startpage and System1: Lying for Almost a Year and Nowadays Making Things Personal/Ad Hominem (Shooting the Messengers)

    As more people become aware of what a scam Startpage is (and has clandestinely been for nearly a year) the strategy seems to be further obfuscation and even personal attacks (demonising the critics/exposers)



  3. When You Cannot Convert GNU/Linux Into Windows (Mono, DLL Files Etc.) You May Try to Make It Subservient to Windows (Vista 10 and WSL)

    Microsoft needs people outside Microsoft to promote WSL; some of them have already entered GNU/Linux companies



  4. IRC Proceedings: Sunday, December 15, 2019

    IRC logs for Sunday, December 15, 2019



  5. GitHub is All About Control

    GitHub is not a platform for sharing and collaboration but social control and manipulation of the Free software community



  6. 2019 in Review: Worst Year Ever for Software Freedom

    A look back (and ahead) as the year's end fast approaches, marking the end of a mostly bad year



  7. Links 15/12/2019: Hacker-Friendly Hardware Success Stories and Mozilla Woes

    Links for the day



  8. European Patents Losing Their Appeal, Lustre and Glamour

    Years of assaults on EPO staff — including EPO judges — have taken their toll and the quality of patents is nothing like it used to be



  9. Software Freedom and The U.S. Constitution

    “We need to stand for the freedom to not use the software — we need to enjoy that freedom without giving up the rest of the existing Free software ecosystem.”



  10. IRC Proceedings: Saturday, December 14, 2019

    IRC logs for Saturday, December 14, 2019



  11. Links 15/12/2019: Wine 5.0 RC1 Released, KDE Frameworks 5.65.0, Qubes OS 4.0.2 RC3

    Links for the day



  12. It Matters a Lot What You Call the System

    Why the best name for the best operating system would be "GNU", not "Linux" (media has twisted the words so as to marginalise GNU and its politics/philosophy)



  13. Only the EPO Goes as Far as Bribing Publishers (the Media) to Promote Software Patents and Publish Fictional Stories

    The world’s patent offices are growing tired of granting software patents which courts later toss out (because these patents are not valid); not only does the EPO advocate such patents — typically using a bundle of buzzwords — it’s also bribing the media to help



  14. EU Needs to Show That It Cares About SMEs and Not 'European Champions' That Are Actually Foreign Monopolies

    Judging by the EU’s nearly blind and unconditional support for the management of the EPO — no matter how abusive and corrupt it has gotten — one has to wonder if the ex-EU official in charge of the EPO reveals a profound democracy deficit as well as growing dangers to Europe’s businesses — the productive firms to which patent maximalism often represents far more risk than opportunity



  15. Guest Article: The Free Software Movement Should Come Out From the Box

    "From now onwards we have to think from a user’s rights perspective and mobilise users of Free software. They should know what rights they ought to get."



  16. IRC Proceedings: Friday, December 13, 2019

    IRC logs for Friday, December 13, 2019



  17. Links 13/12/2019: QEMU 4.2.0, GNU Guile 2.9.7

    Links for the day



  18. Links 13/12/2019: Zorin OS 15.1, Vim 8.2

    Links for the day



  19. Linux Foundation Has Outsourced All the Licence Compliance Stuff to Microsoft, a Serial GPL Violator

    OpenChain Specification/OpenChain Project and Automated Compliance Tooling (ACT) are yet more examples -- the latest of many -- of the Linux Foundation being outsourced to Microsoft, not only for code but also documentation and hosting



  20. IRC Proceedings: Thursday, December 12, 2019

    IRC logs for Thursday, December 12, 2019



  21. Copyleft: Keeping Code Free

    Now that news about "Linux" is dominated by promotion of proprietary software we ought to remember what perpetrators of such a strategy seek to eliminate



  22. Plans That Worked, Plans That Failed

    "I am still looking for good news, but the more good I try to find, the more nastiness I uncover. This is by far, Free software's worst year ever. 2019 Sucks!"



  23. Links 12/12/2019: KDE Applications 19.12, Qt Creator 4.11, New VirtualBox

    Links for the day



  24. Brand Dilution in Action

    Microsoft's proprietary software which spies on people and businesses is getting a "free ride" on the "Linux" brand; and nobody seems to care, nobody seems to notice how perverse that it



  25. At the EPO Money -- Not Quality -- is King

    Financiers are ruining quality



  26. The EPO's Strategic Failure 2023

    Potemkin social dialogue



  27. IRC Proceedings: Wednesday, December 11, 2019

    IRC logs for Wednesday, December 11, 2019



  28. EPO Promoting Software Patents in Countries Where These Are Illegal

    The EPO's vision of 'unitary' software patents (patents on algorithms in countries that disallow such patents, as per their national laws) won't materialise, but in the meantime a lot of Invalid Patents (IPs) are granted in the form of European Patents (EPs) and this is wrong



  29. We Support GNU and the FSF But Remain Sceptical and Occasionally Worry About an RMS-less FSF

    Richard Stallman (RMS) is not in charge of the FSF anymore (it's Stallman who created the FSF) and there's risk the decisions will be made by people who don't share Stallman's ethics or the FSF's spirit



  30. Links 11/12/2019: Huawei Lobbied by Microsoft (Because of GNU/Linux) and Microsoft Still Googlebombs Linux to Promote 'Teams'

    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