10.01.07

Gemini version available ♊︎

Novell Selfishly Uses Mono as ‘Protection’-based Advantage

Posted in Microsoft, Mono, Novell, Patents at 8:07 pm by Dr. Roy Schestowitz

Nomo
No Mo’ patents!

Computer Weekly has just published a one-sided article about Mono.

To Mono’s founders, the proprietary/open-source battle was less important than issues of co-existence and the most appropriate platform for the job. According to Justin Steinman, Novell’s director of product marketing for Linux and open platform systems, and the man in charge of selling Mono to the world, “Mono essentially enables you to run .net applications on Linux,” giving you the choice of developing for either platform knowing that it will run on both.

Interestingly enough, the article defends Mono proponents while dismissing opposition to it as being “anti-Microsoft”. Mind you, they use negativism; not “pro-open standard”, not “anti-patents”, not “freedom advocate”, or even “fair competition proponents”.

“Remember that Microsoft has no commitment for Mono.”The article quotes Justin Steinman, whose “night job” (that’s what he calls it) now involves both Microsoft and Novell. This type of duality in role and responsibilities is similar to Miguel de Icaza’s role at Novell, but Miguel describes a duality in a different way, namely: “I have two positions, and one is speaking as the person managing the Mono team, and then there is another answer speaking as a Novell vice president.” It wasn’t long ago that he spoke about OOXML being a “superb standard”.

In any event, remind yourselves why Mono is risky, unlike GNU/Linux and open standards (Novell will try to convince you otherwise, using perceived risk as an ‘advantage’).

…Mono’s role in the deal that of a hook to make customers write .NET applications because they can be run on Linux – only to find later on that they are armless or legless because of a change in the .NET specifications, a change which Microsoft decides not to make public?

Remember that Microsoft has no commitment for Mono. It can pull the carpet from underneath Mono’s feet at any time, so again, as a Mono-reliant customer, you’re left at Microsoft’s mercy.

If you seek evidence of what might come, then read the following.

I read the agreement between Xandros and Microsoft, and one of the excluded products was Mono, so Microsoft promises to not sue Xandros over their distribution but excluding Mono and a few other products, i.e. they reserve the right to sue over Mono. I wonder if this is an interesting preview of on what basis they want to fight the free world.

Interestingly, the Novell deal seems to be different, Mono is not excluded from the Novell deal. So Microsoft seems to be promising not to sue Novell over Mono, but keeps the option open for Xandros. Weird but true.

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.

21 Comments

  1. David said,

    October 2, 2007 at 2:49 am

    Gravatar

    Hi Roy, After reading this post, I fail to see the point of it, regurgitating an old, albeit intresting difference between the several microsoft deals.

    To me the title especially seems over-sensationalised, and fails to deliver. Theres no new evidence in this post of Novell using mono as a competitive advantage.

    Obviously, if I’m missing something, then please correct me.

  2. Roy Schestowitz said,

    October 2, 2007 at 4:26 am

    Gravatar

    David,

    Have a look at this:

    And There You Have It: You Need Novell (Not Just .NET) to Run Moonlight

    While Linux thrives in the sharing of work, Novell seems to be Monopolosing (pun) Mono. Since Novell is claimed to have received special ‘protection’ for “Mono”, I firmly believe that it would be wise to disengage and exclude it from other GNU/Linux distributions. While Jeff Waugh has insisted that GNOME is in no way Mono-dependent, a friend of mine who is a former Fedora maintainer begs to differ, even after hearing Jeff’s rebuttal to my posts.

  3. David said,

    October 2, 2007 at 9:03 am

    Gravatar

    Thanks for replying, Roy. I understand that Novell has the ability to use Mono to prolong dependence on proprietary software and formats, but I don’t see how Mono is any different to Samba or MS-Exchange implementations.

    Or is it that Novell owns the copyright of Mono, and now has perceived clearance from Microsoft to use Mono, that makes this different from other Free implementations of proprietary standards?

    Forgive my ignorance/stupidity ;-) Almost a year after the deal I still don’t understand a lot of the ramifications of it.

  4. Roy Schestowitz said,

    October 2, 2007 at 9:13 am

    Gravatar

    David,

    Have a look at this excellent analysis from MattD. It also includes the Mono promises.

    The Novell/Microsoft Deal Dissected

    Also, of interest you might find the following:

    Dissecting Microsoft’s OOXML/ODF Strategy

    Mindmap: Microsoft Deals and Partnership as Proxies in a Software Battle

  5. Jose_X said,

    September 14, 2008 at 9:46 pm

    Gravatar

    >> I understand that Novell has the ability to use Mono to prolong dependence on proprietary software and formats, but I don’t see how Mono is any different to Samba or MS-Exchange implementations.

    Here is one difference. One is an API, used to build things. The others are specific implementations. Two specific bad apples (for arguments sake let’s assume) vs. the rotting poison that creates bad apples.

    That’s an oversimplification of one of the major differences.

  6. AlexH said,

    September 15, 2008 at 2:18 am

    Gravatar

    @Jose: that’s not true in a theoretical or technical level.

    Samba is entirely about the API. Samba 4 is built out of API descriptions (idl files) and can be used to build things (e.g., OpenChange).

    Mono is no different to GNU Portable.net, gcj, etc.

  7. Roy Schestowitz said,

    September 15, 2008 at 2:23 am

    Gravatar

    Alex,

    Is Samba /actively/ being used to build things, like Novell builds a lot of the desktop with Mono (unlike Mainsoft for example)?

  8. AlexH said,

    September 15, 2008 at 2:46 am

    Gravatar

    I just gave you an example, OpenChange for native MAPI access to Microsoft Exchange.

  9. Roy Schestowitz said,

    September 15, 2008 at 2:52 am

    Gravatar

    I’ve just browsed it a bit [ http://www.openchange.org/index.php?option=com_content&task=view&id=16&Itemid=54 ].

    it seems like a drop-in replacement for Exchange, which is designed to work with existing software. That’s not the same thing as Mono. Here you have protocols that Microsoft commoditised.

  10. AlexH said,

    September 15, 2008 at 3:42 am

    Gravatar

    No, primarily (at the moment) it’s to get clients to talk to Exchange, replacing Exchange comes later.

    Microsoft didn’t commoditise these protocols in any way.

  11. Roy Schestowitz said,

    September 15, 2008 at 3:59 am

    Gravatar

    It made them hard to bypass.

  12. AlexH said,

    September 15, 2008 at 5:58 am

    Gravatar

    Do you just want to explain what you understand “commoditisation” to mean?

    “It made them hard to bypass” doesn’t fit with the definition I use, so I suspect we’re talking at cross purposes somewhat.

  13. Roy Schestowitz said,

    September 15, 2008 at 6:10 am

    Gravatar

    There are a variety of protocols that became almost essential to follow due to the ubiquity of Microsoft software, particularly on the desktop. One example of this is Outlook/Exchange, which the widespread use of Microsoft Office led to. At one later stage, the competition among ‘rival’ protocols hardly exists, but there is no standardisation, either. I think of it (the protocol) as a form of a commodity although it may still involve pricey licensing, such as those that Scalix (Xandros) subscribed to. Other examples worth adding are the wide use of GIF on the Web and x86 on the desktop.

  14. AlexH said,

    September 15, 2008 at 6:29 am

    Gravatar

    I think your use of the word “commodity” is incorrect.

    In terms of protocols, HTTP or TCP/IP are commodity protocols: they are well-known and used in the marketplace, but there are also many different products which implement them. Cars are commodity items in the same way; different people buy different cars for different reasons, but at a basic level they all do the same thing. X86 processors are also commodity.

    Exchange’s protocols are very much not commodity; they are de-facto as you rightly point out, and while some people have licensed the information to use them they’re not replaceable in the market place.

    Indeed, there isn’t really such as thing as “Exchange protocol” anyway. In terms of authentication, you have exactly the same Active Directory/Kerberos setup, which Samba already provides. The IPC mechanism is the same, and it uses the AD tree, and then provides a MAPI API to access actual data.

  15. Roy Schestowitz said,

    September 15, 2008 at 6:36 am

    Gravatar

    This brings us back to the earlier point about whether or not Mono is different from Samba. This comparison was used a lot by Jeff Waugh.

    We can live without Mono because we have popular frameworks like Java. It’s not the same with Samba.

    Also see:

    http://boycottnovell.com/2008/03/09/samba-microsoft-eu-tricks/

  16. Dan O'Brian said,

    September 15, 2008 at 7:30 am

    Gravatar

    Moonlight and Mono are also separate products, so your logic fails to deliver.

    Here’s my theory:

    Only Novell can deliver Moonlight (as defined by the product Novell is implementing + the Microsoft codec binary blob) because Microsoft only gave Novell the right to redistribute the binary blob and it comes with a number of other restrictions as well.

    There’s nothing that suggests that distributions could not ship Moonlight sans binary codec blob that I’ve seen.

    Of course, for distributions to do so, they would have to link with, say, ffmpeg to make it feature-complete and by doing so put themselves at legal risk unless they also licensed the video formats (from Microsoft and MPEG) because the video formats are patented.

    AFAICT, the risk of other patents applying to Silverlight should be fairly minimal because there’s nothing that Silverlight does that does not have “prior art” written all over it (e.g. 2D vector graphics, gee wiz, SVG maybe? Same with the XAML format – SVG or GladeXML = prior art).

    If Microsoft have patents on Silverlight’s 2D vector graphics, then it is just as likely that Cairo infringes – and Cairo is a core part of the Linux Desktop (and actually, afaik, Moonlight uses Cairo for drawing anyway).

  17. Dan O'Brian said,

    September 15, 2008 at 7:33 am

    Gravatar

    I should mention also that InkScape can read/save XAML and convert between it and SVG and whatever other formats it supports.

  18. Roy Schestowitz said,

    September 15, 2008 at 7:47 am

    Gravatar

    It’s irrelevant to the point that Moonlight requires Mono.

  19. AlexH said,

    September 15, 2008 at 7:47 am

    Gravatar

    @Roy: what you mean is, *you* can live without Mono. And that’s fine, it’s a choice you can make. Others will choose to use Mono, and that’s also fine, because it’s free software.

    @Dan: indeed, the actual output – Flash, Silverlight, whatever, is relatively unimportant.

    What is crucial is that there need to be free software apps for *creating* the content, not just passively consuming it. Inkscape is one app, LunarEclipse is another.

    I personally wish that there was a decent free software tool which did SVG + animation. It looks like we’re a long way from that, though.

  20. AlexH said,

    September 15, 2008 at 7:51 am

    Gravatar

    @Roy: Moonlight doesn’t require Mono unless you’re scripting it, and you can always script it from the outside using Javascript anyway – in that mode, it’s just a fancy canvas. Even Moonlight users can avoid Mono if they wish.

  21. Roy Schestowitz said,

    September 15, 2008 at 7:56 am

    Gravatar

    It’s also possible to use GNU/Linux without X. Would people actually do this? Would /packagers/?

    Look at the URL:

    http://www.mono-project.com/Moonlight

    “A page to track the various projects that make up the Mono-based implementation of Silverlight.”

DecorWhat Else is New


  1. Not Tolerating Proprietary 'Bossware' in the Workplace (or at Home in Case of Work-From-Home)

    The company known as Sirius ‘Open Source’ generally rejected… Open Source. Today’s focus was the migration to Slack.



  2. The ISO Delusion: A Stack of Proprietary Junk (Slack) Failing Miserably

    When the company where I worked for nearly 12 years spoke of pragmatism it was merely making excuses to adopt proprietary software at the expense of already-working and functional Free software



  3. Debian 11 on My Main Rig: So Far Mostly OK, But Missing Some Software From Debian 10

    Distributions of GNU/Linux keep urging us to move to the latest, but is the latest always the greatest? On Friday my Debian 10 drive died, so I started moving to Debian 11 on a new drive and here's what that did to my life.



  4. Stigmatising GNU/Linux for Not Withstanding Hardware Failures

    Nowadays "the news" is polluted with a lot of GNU/Linux-hostile nonsense; like with patents, the signal-to-noise ratio is appalling and here we deal with a poor 'report' about "Linux servers" failing to work



  5. Microsofters Inside Sirius 'Open Source'

    Sirius ‘Open Source’ has been employing incompetent managers for years — a sentiment shared among colleagues by the way; today we examine some glaring examples with redacted communications to prove it



  6. Links 29/01/2023: GNOME 43.3 Fixes and Lots About Games

    Links for the day



  7. The Hey Hype Machine

    "Hey Hype" or "Hey Hi" (AI) has been dominating the press lately and a lot of that seems to boil down to paid-for marketing; we need to understand what's truly going on and not be distracted by the substance-less hype



  8. IRC Proceedings: Saturday, January 28, 2023

    IRC logs for Saturday, January 28, 2023



  9. Unmasking AI

    A guest article by Andy Farnell



  10. The ISO Delusion/Sirius Corporation: A 'Tech' Company Run by Non-Technical People

    Sirius ‘Open Source’ was hiring people who brought to the company a culture of redundant tasks and unwanted, even hostile technology; today we continue to tell the story of a company run by the CEO whose friends and acquaintances did severe damage



  11. Links 28/01/2023: Lots of Catching Up (Had Hardware Crash)

    Links for the day



  12. IRC Proceedings: Friday, January 27, 2023

    IRC logs for Friday, January 27, 2023



  13. Microsoft DuckDuckGo Falls to Lowest Share in 2 Years After Being Widely Exposed as Microsoft Proxy, Fake 'Privacy'

    DuckDuckGo, according to this latest data from Statcounter, fell from about 0.71% to just 0.58%; all the gains have been lost amid scandals, such as widespread realisation that DuckDuckGo is a Microsoft informant, curated by Microsoft and hosted by Microsoft (Bing is meanwhile laying off many people, but the media isn’t covering that or barely bothers)



  14. This is What the Microsoft-Sponsored Media Has Been Hyping Up for Weeks (Ahead of Microsoft Layoffs)

    Reprinted with permission from Ryan



  15. [Meme] António Campinos Wants to Be F***ing President Until 2028

    António Campinos insists he will be EPO President for 10 years, i.e. even longer than Benoît Battistelli (despite having appalling approval rates from staff)



  16. European Patent Office Staff Losing Hope

    The EPO’s management with its shallow campaign of obfuscation (pretending to protect children or some other nonsense) is not fooling patent examiners, who have grown tired and whose representatives say “the administration shows no intention of involving the staff representation in the drafting of the consultant’s mandate” (like in Sirius ‘Open Source’ where technical staff is ignored completely for misguided proposals to pass in the dark)



  17. IRC Proceedings: Thursday, January 26, 2023

    IRC logs for Thursday, January 26, 2023



  18. Sirius Relegated/Demoted/Destined Itself to Technical Hell by Refusing to Listen to the Technical Staff (Which Wanted to Stay With Asterisk/Free Software)

    In my final year at Sirius ‘Open Source’ communication systems had already become chaotic; there were too many dysfunctional tools, a lack of instructions, a lack of coordination and the proposed ‘solution’ (this past October) was just more complexity and red tape



  19. Geminispace Approaching Another Growth Milestone (2,300 Active Capsules)

    The expansion of Geminispace is worth noting again because another milestone is approached, flirted with, or will be surpassed this coming weekend



  20. [Meme] Cannot Get a Phone to Work... in 2022

    Sirius ‘Open Source’ wasted hours of workers’ time just testing the phone after it had moved to a defective system of Google (proprietary); instead of a rollback (back to Asterisk) the company doubled down on the faulty system and the phones still didn’t work properly, resulting in missing calls and angst (the company just blamed the workers who all along rejected this new system)



  21. [Meme] Modern Phones

    Sirius ‘Open Source’ is mistaking “modern” for better; insecurity and a lack of tech savvy typically leads to that



  22. The ISO Delusion: Sirius Corporation Demonstrates a Lack of Understanding of Security and Privacy

    Sirius ‘Open Source’, emboldened by ISO ‘paperwork’ (certification), lost sight of what it truly takes to run a business securely, mistaking worthless gadgets for “advancement” while compelling staff to sign a new contract in a hurry (prior contract-signing scandals notwithstanding)



  23. Links 26/01/2023: LibreOffice 7.4.5 and Ubuntu Pro Offers

    Links for the day



  24. Links 26/01/2023: GNU poke 3.0 and PipeWire 0.3.65

    Links for the day



  25. IRC Proceedings: Wednesday, January 25, 2023

    IRC logs for Wednesday, January 25, 2023



  26. Companies Would Collapse Upon Abandoning Their Original Goals (That Attracted All the Productive Staff)

    Staff with technical skills won't stick around in companies that reject technical arguments and moreover move to proprietary software in a company that brands itself "Open Source"



  27. [Meme] Listen to Your Workers, Avert Disaster

    Companies that refuse to take input from staff are doomed to fail



  28. The ISO Delusion: When the Employer Doesn’t Understand the Company's Value Proposition (Building Systems) and Rejects Security

    Sirius ‘Open Source’ has failed to sell what it was actually good at; instead it hired unqualified people and outsourced almost everything



  29. Links 25/01/2023: NuTyX 23.01.1 and GNU Guile 3.0.9 Released

    Links for the day



  30. Links 25/01/2023: Stratis 3.5.0 and Many Political Links

    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