Commentary

Serdar Yegulalp
 

A Difference That Makes No Difference From Open Source ...

I couldn't let the "divide and conquer road map" for keeping open source at bay, as described by my colleague Randy George, pass without comment. The more proprietary software comes to superficially resemble open source, the harder it will be for people to see the benefits of the latter.

I couldn't let the "divide and conquer road map" for keeping open source at bay, as described by my colleague Randy George, pass without comment. The more proprietary software comes to superficially resemble open source, the harder it will be for people to see the benefits of the latter.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

One thing that Randy pointed out stood out the most:

The paper also makes the point that established commercial players can beat open source at its own game by offering free base versions of a product to build up the user base, then segment advanced product features and package them into premium offerings. Hmmm, sounds a little like what open source based startups are doing as well.

True, except that the free versions in question are not themselves open source -- although for the people who just want to Get Work Done, having a free-but-not-open version of the product is often more than enough. Consider Microsoft's SQL Server Express edition vs., say, MySQL: if you're not married to either platform to begin with, and you don't particularly care about lock-in, the former may just seem like one good option among many. And Microsoft has incrementally ramped up competition with open source database solutions, if not by adding features then by taking away restrictions. (For a while, SQL Server Express could not be used for an Internet-facing application, but Microsoft wisely did away with this proviso.)

So is open source itself doomed? Probably not. What I do see happening, though, is the gap between proprietary and open source narrowing from both directions, which will make the choices that much more arbitrary for people who are not especially interested in waving the open-source flag.

On the proprietary side, you'll have closed-source programs, but ones that publish their APIs and employ open standards, protocols, and data formats -- although whether they do all that as a serious bid for positive competition or just a way to ward off potential criticism is going to be anyone's guess. On the open-source side, you'll see two things: open-source core products with for-pay / closed-source enterprise functionality (e.g., MySQL), and entirely open products with the only for-pay element being services and support (e.g., Ingres).

And in the middle are all the people who have to choose between one or the other. And, again, everyone who's not inclined to choose open source for whatever reason is going to find it even more of a toss-up. What's a little vendor lock-in down the road when you can get everything you need done now? A difference that doesn't seem to make a difference is no difference.

That's the challenge to come: for open source developers to find differences that will make a difference -- visibly.


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