Commentary

Serdar Yegulalp
 

The Real Cost Of Open Source Is...?

Word has been circulating about a Standish Group research report that's apparently guaranteed to turn heads.  "Free Open Source Software Is Costing Vendors $60 Billion" is apparently one of the claims made in this report, titled "Trends in Open Source," and while I haven't been able to get my hands on it, the press blurbs about it make me wonder what really is the best way to quantify open source adoption.  Talking about it as "lost" revenue doesn't seem to make much sense.

Word has been circulating about a Standish Group research report that's apparently guaranteed to turn heads.  "Free Open Source Software Is Costing Vendors $60 Billion" is apparently one of the claims made in this report, titled "Trends in Open Source," and while I haven't been able to get my hands on it, the press blurbs about it make me wonder what really is the best way to quantify open source adoption.  Talking about it as "lost" revenue doesn't seem to make much sense.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Here's an excerpt from the Marketwire press release about the report:

"Open Source software is raising havoc throughout the software market. It is the ultimate in disruptive technology, and while it is only 6% of estimated trillion dollars IT budgeted annually, it represents a real loss of $60 billion in annual revenues to software companies," said Jim Johnson, chairman, The Standish Group International.

Part of the reason why I eye the "loss of $60 billion" figure with a bit of suspicion is because it's always notoriously difficult to quantify what you're not selling.  If I use MySQL in house, and never even considered Oracle or SQL Server as a possibility, how does that translate into a loss for those two companies?  The biggest way I can see such a thing being quantified is if Standish is talking to people who, say, were already using a proprietary product and then switched away to an equivalent open source product.  That would be the most sensible way, from what I can tell, to quantify actual loss, especially since any hard numbers about open source adoption are always difficult to obtain and typically rely on self-reporting

But even that's not a complete picture, either.  If an open source product competes directly with what I offer, that's not much different from losing revenue to a commercial competitor: it's still an incentive for me to make a better product that people will want to pay for, or to change my business model in the long run if that's viable.  The source of the competition isn't terribly relevant when it translates out to the same thing in the end: evolve or die.

One other thing that towers over all of this, in my mind, is that every software vendor also is a software consumer.  If I sell a proprietary, closed-source software product (for instance, a high-end multimedia app), but I use open source software internally as a cost-savings measure, I still benefit from open source. So if open source is "raising havoc," as Mr. Johnson puts it in the quote above, it's putting money back into at least as many pockets as it is allegedly taking from them.


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