Commentary

Charles Babcock
InformationWeek  

All That Got Stolen Was Microsoft's Thunder

It's bad enough that Microsoft with its big war chest might sue you for producing open source software. But what's really hard to take is the suggestion that you stooped to stealing Microsoft code for your project. At the Open Source Business Conference this week in San Francisco, one show organizer got his revenge.

It's bad enough that Microsoft with its big war chest might sue you for producing open source software. But what's really hard to take is the suggestion that you stooped to stealing Microsoft code for your project. At the Open Source Business Conference this week in San Francisco, one show organizer got his revenge.When Microsoft says open source code infringes its patents, it's a hard charge for Linux kernel developers to defend themselves against. On the one hand, Microsoft won't say what code and which patents. On the other, it makes a charge that caters to a residual cynicism in the old guard of enterprise IT ranks. Volunteer open source programmers couldn't possibly have done all the work they're credited with doing. Maybe someone, somewhere, lifted Microsoft code and added it to his open source code project.

The best response I've seen was from Jonathan Corbet at a panel at the Open Source Business Conference in San Francisco last May. Corbet is a Linux kernel developer himself and executive editor of the Linux Weekly News.


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

"I feel I've been called a thief," he said levelly during a panel at the event, and pointed out that Microsoft was one of the companies that had patented "thousands of trivial functions ... There's no way to write a nontrivial program that can't be claimed to infringe on someone's patents."

Other open source code programmers answered the insinuation by saying, "Show us the infringed code and we will rewrite it." It's a point of pride that developers could quickly rewrite something that smacked of coming too close to a claimed Microsoft patent; volunteers would be waiting in line for the opportunity.

All of which has prompted Microsoft executives, as best I know, to shelve the infringement charge. It's still looking to get willing Linux distributors, like Novell, to sign a deal that says they will be protected from any Microsoft patent action. But Red Hat refuses to do so. If its fiscal 2008 results are any indication, Red Hat is getting more business for having the courage of its convictions. Microsoft's author of the charge, Brad Smith, general counsel, senior VP and corporate secretary, addressed this year's Open Source Business Conference Tuesday and declined to repeat what he had told Fortune magazine a year ago.

There's a lot of open source code running on Windows now, so much that Microsoft wants to forget about those claimed infractions and work more closely with open source developers. Smith said Microsoft believes in the patent system and won't back off its patent portfolio. But at the same time he acknowledged Microsoft has a lot to lose if it doesn't achieve greater harmony with open source communities. Smith made as good a case as he could, and open source developers and users listened, more or less respectfully. But just before Smith spoke, Matt Asay, OSBC program chair, got in a little sly revenge.

If you listened carefully, you could hear this refrain on the public address system above the pre-keynote hubbub, "When we want something, We don't want to pay for it." The name of the song -- "Been Caught Stealing" by the rock & rollers, Jane's Addiction.


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