Commentary

Serdar Yegulalp
 

Microsoft and Open Source ... Happy Together?

"Microsoft" and "open source" have, for a long time, not been two words you would typically breathe in the same sentence.  And now I find myself reading an IWeek piece in which one of Microsoft's open-source point men, Bill Hilf, speaks up on both subjects.

"Microsoft" and "open source" have, for a long time, not been two words you would typically breathe in the same sentence.  And now I find myself reading an IWeek piece in which one of Microsoft's open-source point men, Bill Hilf, speaks up on both subjects.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

I'd been aware of Hilf and his position at Microsoft before, thanks to (among other things) the Port 25 blog, where he and other Microsoft folks post about their work in that company's open-source lab.  Here and there, Microsoft is doing some very good work with certain open-source vendors -- the PHP folks come to mind, for instance.  The good stuff is the nitty-gritty.  But the policy-level material, as always, remains problematic.

A few of Hilf's comments stood out as examples of both of these tendencies, sometimes simultaneously.  He cited Red Hat Enterprise Linux as an example of a direct competitor -- not specifically because of its internal features, but as a platform on which people could run open-source software.  That's been the main horn Hilf has been blowing -- that Windows can and should be a platform on which people run open-source products of many kinds, from the aforementioned PHP to MySQL to you-name-it.  As long as Microsoft stays on that particular subject, it will do just fine.

It's when Microsoft goes further afield -- like its ongoing Linux patent Catch-22 (evidently it learned from SCO that you can't just sue people outright without opening 55-gallon drums of worms) that things get hairy all over again.  But when you get down to it, I'm not sure Microsoft's attitude toward open source is all that different from many other companies whose main interest isn't in open source per se, but in getting what they can from open source.  The attitude, spoken or not, is: What's in it for us? 

It's looking to open source to see what it can get out of it, just like anyone else.  It just happens to be in a position that makes that behavior all the more influential on the software world as a whole.

Another thing that emerged from reading that piece was a clearer picture of the kind of monopoly Microsoft has, or wants to have: a support monopoly.  As long as its offerings remain closed-source and are kept up-to-date by them, Microsoft is the only one who can continue to legitimately claim to support them, and that's how it wants it.  One possible contrast for this was a recent bit of friction between Oracle and Red Hat, where Oracle submitted patches for what it felt were Linux bugs and Red Hat disputed the issue.  I read elsewhere a trenchant criticism of the Linux world as a whole that asserted the single biggest problem is the near-total lack of accountability for fixing some of the simplest things.  To use a piece of parlance I hate, Microsoft (and Apple, too) are deeply reluctant to "allow their brands to be diffused".

I finally wondered if the things Microsoft does with (and to) open source, both good and bad, may well serve as models for future behavior by other companies.  Not everyone who uses open source, or even supports open source (even if indirectly) is going to be a friend of open source -- at least, not a friend in the way most open-source supporters would like them to be.  But that goes with the territory. If you put it out there for everyone to use and work with and potentially support, that means everyone.  Microsoft included.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links