09.19.08

Gemini version available ♊︎

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

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

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.

DecorWhat Else is New


  1. Links 16/10/2021: Xubuntu 21.10 and DearPyGui 1.0.0

    Links for the day



  2. DuckDuckGo’s HQ is Smaller Than My Apartment

    Guest post by Ryan, reprinted with permission



  3. Post About Whether Vivaldi is a GPL violation Was Quietly Knifed by the Mods of /r/uBlockOrigin in Reddit

    Guest post by Ryan, reprinted with permission



  4. The EPO’s Overseer/Overseen Collusion — Part XIII: Battistelli's Iberian Facilitators - Spain

    The EPO‘s António Campinos is an ‘Academy’ of overt nepotism; what Benoît Battistelli did mostly in France Campinos does in Spain and Portugal, severely harming the international image of these countries



  5. From Competitive (Top-Level, High-Calibre, Well-Paid) Jobs to 2,000 Euros a Month -- How the EPO is Becoming a Sweatshop by Patent Examiners' Standards

    A longish video about the dreadful situation at the EPO, where staff is being ‘robbed’ and EPO funds get funnelled into some dodgy stock market investments (a clear violation of the institution’s charter)



  6. [Meme] Protecting European Patent Courts From EPO 'Mafia'

    With flagrant disregard for court rulings (or workarounds to dodge actual compliance) it seems clear that today's EPO management is allergic to justice and to judges; European Patents perish at unprecedented levels in national European courts and it should be kept that way



  7. Links 15/10/2021: Pine64's New PinePhone Pro and Ubuntu 22.04 LTS Codename

    Links for the day



  8. [Meme] GitHub Isn't Free Hosting, It's All About Control by Microsoft

    Deleting GitHub isn’t a political statement but a pragmatic decision, seeing how Microsoft routinely misuses its control over GitHub to manipulate the market



  9. With EPO 'Strike Regulations' Belatedly Ruled Unlawful, EPO Management May be Lowering the Salary Even Further by Introducing Outside 'Temps' or Casual Workers

    Institutional capture by an 'IP' (litigation) Mafia is nearly complete; with illegal so-called (anti) 'Strike Regulations' out the door, they're quickly moving on to another plan, or so it seems on the surface



  10. Links 15/10/2021: 95% of Ransomware Targets Windows

    Links for the day



  11. IRC Proceedings: Thursday, October 14, 2021

    IRC logs for Thursday, October 14, 2021



  12. The EPO’s Overseer/Overseen Collusion — Part XII: The French Connection

    The EPO‘s presidency (led by Frenchmen for nearly 15 years out of the past 18 years; Benoît Battistelli and António Campinos are both French despite their somewhat misleading surnames) is extremely unlikely to even be mildly scrutinised by the French delegates because of a web of nepotism and protectionism



  13. [Meme] Another Maladministration Meeting Comes to an End

    Did the EPO‘s overseeing body properly tackle Benoît Battistelli‘s illegal acts, authorised by that very same overseeing body? Don’t hold your breath as António Campinos continues to crack down on staff (maybe ILOAT will rule on it in 2030)



  14. Links 14/10/2021: LibreOffice 7.2.2, Happy Birthday to Jolla, Ubuntu 21.10, Devuan GNU+Linux 4.0, OpenBSD 7.0

    Links for the day



  15. [Teaser] What Miguel de Icaza Really Thinks of the CEO of Microsoft GitHub

    Following the opening of a new series about Microsoft GitHub we drop a little teaser today; we expect dozens of parts to be released in the coming weeks/months as facts are being validated and organised



  16. Splitting the Time to Cover More Leaks and Exposés

    We take stock of Part 11 of the ongoing EPO series (“EPO’s Overseer/Overseen Collusion”) and explain what caused various delays yesterday; we may have to up our pace a little in order to keep up with an influx of leaks and whistleblowers



  17. [Meme] Destroying the Workplace

    The working conditions at the EPO continue to worsen under the António Campinos regime, perpetuating the decade-long 'demolition project' of Benoît Battistelli and his cohorts in the complicit Administrative CouncilThe working conditions at the EPO continue to worsen under the António Campinos regime, perpetuating the decade-long 'demolition project' of Benoît Battistelli and his cohorts in the complicit Administrative Council



  18. Microsoft GitHub Exposé — Part I — Inside a Den of Corruption and Misogynists

    Today we commence a new series that implicates Microsoft, GitHub, Copilot, and Team Mono



  19. EPO Management Tricks EPO Staff Into Taking More Paycuts

    “Education and childcare reform” [sic] is an António Campinos "reform" in the same sense regressive salary reductions are just “adjustments” (euphemism); Electronic opt-in gaffes, according to staff representatives, show that the tradition of Benoît Battistelli carries on at the Office, taking away from staff for a few corrupt officials to milk the institution to death



  20. Links 14/10/2021: Whisker Menu 2.6.1 and KDE's Birthday

    Links for the day



  21. Links 14/10/2021: DragonFly 6.0.1 Released and Red Hat Loses Another Top Executive

    Links for the day



  22. IRC Proceedings: Wednesday, October 13, 2021

    IRC logs for Wednesday, October 13, 2021



  23. Süddeutsche Zeitung Became a Propaganda Arm of EPO Management (and by Extension Software Patents/Patent Lobbyists)

    EPO ‘genius’ António Campinos enjoys shallow press coverage, which echoes or resembles Benoît Battistelli‘s corruption of the media (paid-for fluff)



  24. GNOME (and Debian) Infringe Human Rights by Shipping Parental Control Software (Internally Called “Malcontent”)

    Guest post by Ryan, reprinted with permission



  25. No, JWZ, Discord is Not “IRC With Pictures”

    Guest post by Ryan, reprinted with permission



  26. The EPO’s Overseer/Overseen Collusion — Part XI: “General Bock” - Battistelli's Swiss Apprentice?

    The António Campinos-led EPO won’t be subjected to real oversight by the Administrative Council, which ‘met’ (online) earlier today; so we look at who in the Administrative Council did what; today we wrap up the parts about Switzerland (third part of three)



  27. Links 13/10/2021: Sparky 2021.10 and New Archcraft

    Links for the day



  28. Links 13/10/2021: Firefox Keylogger on (By Default), GNOME Platform Design Discussed

    Links for the day



  29. [Meme] [Teaser] Swiss Alexandre Benallas

    The EPO‘s French dictator, Benoît ‘Vichy’ Battistelli, might be relieved to hear that his enabler in the adjacent Switzerland also enlisted armed bullies to keep the population down (the father of António Campinos might know a thing or two about those; it’s why he fled to France)



  30. IRC Proceedings: Tuesday, October 12, 2021

    IRC logs for Tuesday, October 12, 2021


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