Commentary

Serdar Yegulalp
 

Open Source To The Rescue In Hard Times

It's a spiel that makes a lot of sense on the face of it. Switch to open source and you'll not only save money (who doesn't want to do that?) but guard yourself against the unexpected repercussions of these financially grim days.

It's a spiel that makes a lot of sense on the face of it. Switch to open source and you'll not only save money (who doesn't want to do that?) but guard yourself against the unexpected repercussions of these financially grim days.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Evidence that big business is turning to open source, in one form or another, is hard to deny. When I spoke with Jim Zemlin last week, he mentioned that an event the Linux Foundation had planned for Wall Street movers and shakers was filled to capacity. (It's an invite-only event; no press, but that's what LinuxCon is for.) Matt Asay detailed similar initiatives on the part of the Oregon Department of Human Services. There's any number of other examples; you can probably cite a few right in your own company.

The big question in my mind is: What specific benefits do the folks reap by making the switch? Cost savings alone is great, but saving money with open source doesn't happen automatically, even if the initial outlay for a given package can approach zero and can happen with minimal effort -- or "friction", as the buzzword goes today.

One additional benefit, which I have not seen discussed much, is the fact that an open source project isn't tied to any one thing. Certainly not any one company. And if there's anything we've learned in the past couple of months, no one company lasts forever. Granted, Red Hat and Canonical and Novell/SUSE aren't issuing mortgage-backed securities as a big part of their business model, but that doesn't make any of them immune from bad tidings. Pick open source for your infrastructure, since that's where most of the open source is being used in enterprises right now, and the risk of being left high and dry goes down that much more.

Granted, even this has limits. If a company that's done an outstanding job of support for an open source project goes bust, the quality of the support you'd get from someone else might not be the same. But it's something, as opposed to crossing your fingers and hoping that whatever proprietary solution you picked doesn't drop dead in two years because the company responsible for it gambled and lost.

If you've deployed open source in your own organization as a way to escape from both the cost and the possible dead-end aspects of proprietary software (especially in these rough times), sound off below.


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