The Novell-Microsoft agreement and .NET

Summary: Microsoft and Novell recently signed a cooperative technology deal that will make it easier for Novell's Suse Linux distribution and Microsoft Windows to work together. In unrelated news, Palestinians and Israelis agreed to end their differences and create a new country called "Palestisrael.

Microsoft and Novell recently signed a cooperative technology deal that will make it easier for Novell's Suse Linux distribution and Microsoft Windows to work together. In unrelated news, Palestinians and Israelis agreed to end their differences and create a new country called "Palestisrael."

Yes, the news that Microsoft would agree to promote long-time competitor Novell's products was surprising. The move does make a lot of sense, however. Linux is an operating system that will exist alongside Windows for the forseeable future. Making those systems work well together is something that customers want and need. Microsoft puts itself at a competitive disadvantage if it hinders such interoperability.

Diving into the particulars, this is good news for Mono, the open source version of the .NET runtime acquired by Novell as part of its purchase of Ximian. If developers were worried before that Mono would run afoul of Microsoft's patent lawyers, those fears should be dispelled. Mono, as a Novell product, is covered by this agreement.

How far will this joint agreement go? Would it extend to helping to port aspects of .NET 3.0 to the Mono platform?

It's an intriguing possibility. Some may believe Microsoft would sooner sign the copyright to Windows over to Richard Stallman. .NET 3.0 is a Windows competitive advantage, the argument goes, and Microsoft will do everything in its power to keep it that way.

Peraps, but Mono wasn't excluded from the recent agreement with Novell. Furthermore, as Joe Wilcox pointed out in a recent blog post, Linux is more a migration path from Unix than from Windows.

I don't see a lot of Linux risk here for Microsoft. JupiterResearch surveys show Linux largely as a migration path from Unix. Very few businesses swap out Windows for Linux, and the number of businesses running Windows Server is increasing.

.NET 3.0 is pretty appealing technology. If the technical professionals migrating to Linux are mostly Unix types, getting them on-board with .NET is certainly a great way to get their feet wet in the "Windows programming universe." .NET 3.0 IS very appealing technology, irrespective of your preference in operating systems.

This is the flip side of the argument I made when describing Mono as a bridge to alternative platforms. While Microsoft gets a chance to have more influence in cross-platform programming interfaces, the fact that other platforms support Windows interfaces mean it is easier for the developer majority to target those other platforms - particularly with a managed code environment like .NET.

Since both sides potentially could benefit from an extension of .NET 3.0 to Linux, the question becomes who is more confident in the respective merits of their platform. Which way would a .NET bridge be more likely to flow? In the aggregate, would the people who prefer Unix / Linux today remain Unix / Linux users even if they find .NET 3.0 to be the coolest technology since sliced bread?

My opinion is that a Linux user is as likely to become a Windows user as a Windows user is to become a Linux user, at least in the medium term. In such an environment, enabling them to be more productive as developers would benefit both parties without creating an undue threat to either.

Topic: Operating Systems

John Carroll

About John Carroll

John Carroll has delivered his opinion on ZDNet since the last millennium. Since May 2008, he is no longer a Microsoft employee. He is currently working at a unified messaging-related startup.

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback

46 comments
Log in or register to join the discussion
  • in unrelated news

    Palestisrael goverment will use the Winlux OS
    mbucuradrian
  • mono e mono

    And now a word from our sponsor:

    [pre]
    ooMMMMMMMooo
    oMMMMMMMMMMMMMMMoo
    MMMMMMMMMMMMMMo"MMMo
    "MMMMMMMMMMMMMMMMMMMMM
    MMMMMMMMMMMMMMMMMMMMMMo
    MMMM""MMMMMM"o" MMMMMMM
    MMo o" MMM" oo ""MMMMM
    MM MMo MMM" MMoM "MMMMM
    MMo"M"o" "" MMM" oMMMMM"
    oMM M o" " o "o MMMMMM"
    oM"o " o " o "o MMMMMMM
    oMMoM o " M M "o MMMM"MMo
    Mo " M "M "o" o MMMoMMMo
    MMo " "" M " MMMMMMMo
    oMM" "o o " MMMMMMMM
    MMM" MMMMMMMMo
    oMMMo "MMMMMMMMo
    MMMMM o " " o" "MMMMMMMMMo
    MMMMM " " "MMMMMMMMMo
    oMMMM ""MMMMMMMMMo
    oMMMM o o MMoMMMMMMM
    MMMM o "MMMMMMMMMM
    MMMM" o o o "MMMMMMMMMMo
    oMMMMM MMMMMMMMMMo
    MMM"MM Novell/Microsoft "MMM"MMMMMMM
    MMMMMM " o " MMMMMMMMMMM
    "o "ooo o o o"MMMMMMMMoM"
    " o "o "MMo " o" MMMMMMMM"
    o "o" o o " MMMo o o""""MMMM"o" "
    " o "o " o o" " MMMMoo " o "o M"" M "o " "
    "o o" " o o" " " "MMMM" o M o "o" o" o" " o
    M o M " o " " " " MM"" o oMo"o " o o "o " "o "
    o" o " "o " " M " " o MMMMo"o " o o o o" o o" "
    o" "o " o " " o o" M "oo ooMMMMMMM o "o o o " o o o "
    M "o o" o" "o o o " o"oMMMMMMMMMMMMMMMMMMMo" o o "o "o o"
    "" "o"o"o"o o"o "o"o"oMMMMMMMMMMMMMMMMMMo"o"o "o o"oo"
    "" M Mo"o"oo"oM"" " MMoM M M M
    """ """ " """ "

    [/pre]
    D T Schmitz
  • Or it could go completely different.

    First, Novell throws out MONO because it is open source.

    Next MS helps Novell develop a PROPRIETRY .NET 3 run time for Suse that becomes part of the Novell stack.

    All of a sudden Novell/SuSe can do something no other Linux distro can do. Taking it a step further, MS releases Visual Studio to run on Novell Linux (but not other distros).

    At that point the other distros are a foot note in history.
    No_Ax_to_Grind
    • True

      Microsoft wouldn't have to make a .NET 3.0 part of the open source base. I doubt they would ditch Mono. That already exists on Linux, and has a certain amount of popularity. They might, however, create a fee-based .NET 3.0 runtime (that is included free with SUSE) that runs atop Mono.

      I'm not sure how it would play out, but I do think the possibility is there.
      John Carroll
      • Hmmm, given a choice...

        Here is the offer Novell, you can use MONO and all it's limitations, or you can strip it out and use a MS backed version of .NET 3.

        Seems like a no brainer to me.
        No_Ax_to_Grind
    • throw out an open source project?

      then they might have to throw out their Linux distro...
      Voodoo187
      • Why?

        There are distros without MONO in it.
        No_Ax_to_Grind
        • because

          GPL license says that you keep the license intact when you modify the licensed software. Which means MS' .NET for linux would have to be GPL'd if it is included with the distro. Which is why Sun's java isn't included with any Linux, they actually include Blackdown's JRE. Which is why sun is open sourcing java.
          Voodoo187
          • Buzzzzt wrong...

            There are all sorts of proprietary "stacks" with PATENTS running on the Linux kernel.
            No_Ax_to_Grind
    • They could try that

      but I would like to think that customers would understand that this would be another bait and hook trick. If it's proprietary, support could be abruptly halted at any time, giving people with .NET programs no choice but to use the MS products.

      I'm not saying this strategy would fail, because if .NET is really that good then that might be a risk worth taking. I would certainly consider taking that risk if I found the good outweighed the potential bad, but I'd be much more likely to use .NET on Linux if it were open sourced. I guess the question is whether MS feels that overall adoption of .NET will gain them more customers in the long haul than a bait and hook trick, or vice versa.
      Michael Kelly
    • Why throw out something you can make money on?

      Linux and Mono ARE and ALWAYS WILL BE commodity software. That means they will work well for mundane tasks, but if I really want to get something done, I will need some sort of proprietary tools on Linux and I may even need a proprietary OS like Windows. So picture Linux and Mono in a world where they become entry level software that costs MS nothing BUT which tend to enhance the market for more powerful tools which MS will be readily able to supply. For example, I can see Linux users getting hooked on Mono functionality and coming to the point where they want more. An instant market for SuSE AND its enhanced, MS licensed capabilities. Or at some point perhaps, an instant market for another distro PLUS an MS licensed add on. No reason to limit this to SuSE, after all, MS already has licensing agreements with Linspire for example. Another big plus for MS is that companies using Linux, especially SuSE Linux, will be MUCH MORE LIKELY to look to MS for enhanced solutions involving Windows if MS is not perceived as being 'anti-Linux'. In fact Novell and MS can now cross-refer their clients. In the end low cost commodity software intelligently deployed will only serve to leave more money in the IT budget for proprietary enhancements. Lower software overhead will mean more growth and as a result more demand for those proprietary upgrades and the MS rep will be well positioned to market them. In spite of what many are saying (I know that PJ over at Groklaw is all worked up about this) I think this is a great day for Linux AND a great day for MS. Why pay the lawyers any more money than we have too? All the money the lawyers make off of MS vs opensource is money that won't get spent on software, duh? I understand why opensource is scared of MS AND I also understand why MS is scared of opensource, but finally we are beginning to see a breakthrough where both sides can live in harmony and make money (perhaps even more money) while they're at it. So it wouldn't surprise me to see "Genuine" .Net for Linux before long for those who just want more than what Mono can deliver.
      George Mitchell
  • .Net a non-issue

    When is the world going to learn not to use .NET?
    ahinkle
    • Obviously you aren't a programmer.

      Yeah, it shows in your statement.
      No_Ax_to_Grind
      • Obviously you aren't a communicator

        It shows in your lack of statements.
        Joeman57
        • Not to worry, the smart ones got it.

          Sorry you were not amoung them.
          No_Ax_to_Grind
      • I fail to see the advantage

        I think the concept was good at time but it really kind of turned into hassles.

        For example.

        I have .net 1.0 apps, 1.1 apps and few 2.0 apps. Installing the framework for 2.0 breaks some of the 1.0 apps. Also you have to make sure you have the right frameworks installed. It's really confusing at time with vendor documentation that is cryptic as HE double hockey sticks.

        I don't know if this problem is Microsoft's or bad programming on the vendors part. I suspect the vendor is problem though.

        I don't do .NET programming so I'm really just going on what I've experience with Vendors and their use of the .Net frameworks.
        voska
  • Never quite understood

    What's the advantage of a managed-code environment that is supposed to be MS's answer to Java when it only runs on a single platform?
    Robert Crocker
    • Simple really...

      That single platform covers 90% - 95% of all users. ;-)
      No_Ax_to_Grind
      • Plus...

        ...that platform is spread across all the devices Microsoft supports - mobile phones, handhelds, set-top boxes, tablet PCs, portable media centers, game consoles, etc. etc. etc.

        It is that simple equation that Sun did not understand properly, to its detriment.
        John Carroll
        • No it isn't

          This "platform" might be spread across all the devices that MS releases from this point forward. Seeing as how .NET 3.0 is only now being released and only supports XP SP 2 and Vista for desktops that leaves a lot of people out in the cold.

          Now the next question, with so many mobile phones already running Java why would you want to develop on .NET for devices that MIGHT support it in the future?

          I'd actually contest your final conclusion. Sun understood that issue much better than MS did. They realized that they could not exercise a realistic level of control over all the various platforms so instead they created an intermediate VM that device manufacturers were free to implement.

          MS once again is trying to force feed a one-size-fits-all solution onto other devices strictly through the strength of their desktop monopoly.
          Robert Crocker