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.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
in unrelated news
mono e mono
[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]
Or it could go completely different.
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.
True
I'm not sure how it would play out, but I do think the possibility is there.
Hmmm, given a choice...
Seems like a no brainer to me.
throw out an open source project?
Why?
because
Buzzzzt wrong...
They could try that
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.
Why throw out something you can make money on?
.Net a non-issue
Obviously you aren't a programmer.
Obviously you aren't a communicator
Not to worry, the smart ones got it.
I fail to see the advantage
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.
Never quite understood
Simple really...
Plus...
It is that simple equation that Sun did not understand properly, to its detriment.
No it isn't
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.