Commentary

Serdar Yegulalp
 

Kiss SCO Goodbye, Again


Follow me on Twitter: http://twitter.com/syegulalp

I'm wondering how many nails have to be pounded into SCO's coffin before people finally just take a stake and pound one through its heart. But one of the last nails has been driven in and sealed over: SCO's lost to Novell in a way that may be, gratefully, irreversible.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

The short details: SCO owes Novell upwards of $2.5 million, and SCO's claims of breach of contract, copyright infringement, and unfair competition have all been dismissed with prejudice -- meaning they can't be brought back even on appeal. There are other things they could resurrect on an appeal, but that takes money -- the one thing they probably have even less of at this point than good will or a future. SCO has been nothing but a name for a long time now, a symbol of how litigation alone is not a business model.

Groklaw, as usual, has its typically fine-grained analysis of what's going on, and debates the next moves for both parties. In Novell's case, it could continue to squeeze blood from this particular stone -- but that to me smacks of a dead horse being beaten until it's turned to glue.

To me, the biggest sign that SCO never had much of a case to begin with is how the world simply chose to move on while all this ground its way through the courts. No one I've spoken to who uses Linux in a business capacity has cited the SCO case as a reason to be worried about Linux's future. It simply wasn't a realistic prospect for them, and now that I look back on it, it never should have been. It was all hot air, and there wasn't even enough of it to fill a balloon.

It's all a sign of growing up. Open source is no longer just an eccentricity, but a serious and powerful way to engineer and distribute software. High time we all accepted this and worked with it.


Follow me on Twitter: http://twitter.com/syegulalp


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