Commentary

Serdar Yegulalp
 

When Is More Open Source Too Much?

It seems like once every few months there's another round of muttering about whether or not the open source world is just too diverse for its own good. Matt Asay at CNet called it the "too many scratches for too few itches" problem. And my own colleague Alex Wolfe so memorably described the world of Linux distributions as "a forking mess" a while back. So, is more really too much, especially now that Linux is edging into the mainstream?

It seems like once every few months there's another round of muttering about whether or not the open source world is just too diverse for its own good. Matt Asay at CNet called it the "too many scratches for too few itches" problem. And my own colleague Alex Wolfe so memorably described the world of Linux distributions as "a forking mess" a while back. So, is more really too much, especially now that Linux is edging into the mainstream?


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Like a lot of questions, the answer you get seems to depend not on who you ask, exactly, but what they want to do at any given point. The folks who grouse about duplication of effort and redundancy of functionality in open source are not doing so at the sole exclusion of the people who want diversity and choice, because there's nothing that says they're the same people at different points in time.

In the abstract, yes, two hundred Linux distributions is too many if you're only looking to run one. But most people will never bother to sift through two hundred in the first place-- they'll generally choose from a pool of three or four, if even that many, which closely fit their needs, based on guidance from an expert. Need a business desktop? Red Hat, or Novell SuSE. Need something for grandma? Ubuntu, or maybe gOS. Need something for the machine in the closet? Puppy Linux, or DSL. And so it goes.

It's the decision-making process that matters most, not the fact that there are "too many" choices. Sure, it doesn't hurt to promote standards that prevent further splintering and duplication of work -- but there needs to be more outreach from experts to help people make decisions about what's best for them. I fear that software developers themselves may not be the best people to do this, since they may well have a vested interest in supporting their project over someone else's.

I'd rather see more effort devoted to aiding people intelligently choose from existing open source solutions than trying to narrow down the total number of choices. If one of open source's big advantages is the way it stimulates plurality of choice to begin with, why give that up?


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