Commentary

Serdar Yegulalp
 

How Is Open Source Like The Large Hadron Collider?

Answer: you start using it, and it sucks everything else up into a black hole. If that sounds like a cheap shot, consider this column by Gene Quinn of IPWatchdog.com: "Open Source Race to Zero May Destroy Software Industry." That's a scary headline if there ever was one, and I read the piece with the growing sense that I had Heard This One Before. I had, just in a different skin.

Answer: you start using it, and it sucks everything else up into a black hole. If that sounds like a cheap shot, consider this column by Gene Quinn of IPWatchdog.com: "Open Source Race to Zero May Destroy Software Industry." That's a scary headline if there ever was one, and I read the piece with the growing sense that I had Heard This One Before. I had, just in a different skin.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The article revolves around the following premises, which I have quoted from him and scaled down a bit for space:

1. "There is a realistic ceiling on the revenue that can be earned by any open source company, and that ceiling is much lower than any proprietary software company."

2. "The trouble with freeware is that there is no margin on free, and while open source solutions are not free, the race to asymptotically approach free is on."

3. "Open source solutions are forcing down pricing. ... As zero is approached, however, less and less money will be available to be made, proprietary software giants will [have] long since gone belly-up and leading open source companies, such as Red Hat, will not be able to compete."

Notice anything missing from this picture? There's no mention at all of one of the major revenue-generating systems used by companies that deal in open source: support and services. There's almost certainly less money to be made there than there is in charging for the software and the support -- but for a company that knows this from the outset, this isn't a problem, since odds are they're already running trim enough to deal with that.

But there's a much bigger omission under that: the race to zero theory only works if every piece of free software drives its proprietary equivalents out of the marketplace, and if those free equivalents cannot be monetized in any way through the sale of support, expertise, etc.

This isn't happening, and frankly I doubt it could. Microsoft is still selling licenses for Windows despite Linux, and Adobe still sells licenses for Photoshop despite GIMP and Paint.NET and all the rest of them. SugarCRM likewise hasn't driven folks like Salesforce.com out of business; if anything, it's given them all the more incentive to be innovative and competitive, to give people something worth paying good money for. And, likewise, the competition between open source firms that provide similar products (e.g., the CMS space) is lively and strong.

Most of the folks who have been driven off the playing field are people making easily-commoditized products. It's silly to pay $50 for a DVD burning application or something equally by-rote when there are tons of perfectly functional free equivalents -- but paying $200 or $4,000 for something which cannot be had for free, either in a decent edition or in any form, makes plenty of sense.

I don't want any of this to be construed as an argument against criticizing open source when used as part of a business strategy. There's plenty of room for good, cogent criticism of open source, and there ought to be. But I've been hearing exactly this kind of chicken-licken-the-sky-is-falling alarmism often enough to become certain it doesn't count as such.


InformationWeek Analytics has published an independent analysis what IT and corporate professionals are looking for in business optimization. Download the report here (registration required).


Follow me and the rest of InformationWeek on Twitter.


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