Commentary

Serdar Yegulalp
 

Sun Continues To Fade

You know you're in trouble when you make the technology pages of the New York Times with a piece about how much money you're bleeding. Such is the case with Sun, which reported a $1.7 billion loss for the first quarter of 2008. And that's not the worst of it.

You know you're in trouble when you make the technology pages of the New York Times with a piece about how much money you're bleeding. Such is the case with Sun, which reported a $1.7 billion loss for the first quarter of 2008. And that's not the worst of it.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

In theory, Sun should be doing great. With cloud computing and SaaS being the Next Big Things, its hardware ought to be flying off the shelves to power all of that. And it's not as if its hardware sales are dismal -- it is still able to sell its iron at a respectable pace -- but it's not the only way to power the cloud, and people understand that now. That's the first big problem, and it will continue to gnaw on them as everyone casts gloomy looks at their balance sheets and sits down for long, sad talks with their accountants.

The other big millstone around Sun's neck has turned out to be Solaris, which it has open-sourced in an attempt to get wider adoption for it, but has been greeted largely with indifference. That's not because Solaris is no good, but because the potential audience for OpenSolaris already has Linux. Turning Java into an open-source offering (however painful and drawn-out the process) has proven to be the better deal, because it's that much more portable, flexible, and genuinely useful. Solaris may be more adept than Linux at heavily multithreaded server environments, but I've gone blue in the face before talking about how IT history is littered with technically superior products that got eaten alive by more properly marketed competitors.

One of the options outlined in the above article is to sell off its legacy server business to Fujitsu. That might buy Sun some time -- literally and figuratively -- but at the possible cost of alienating more of its existing base. Who's to say its other customers won't effectively be sold off to the highest bidder as well?

Selling off pieces of the company doesn't address the underlying problem: Sun still thinks it's irreplaceable. Nobody else offers Solaris, or the types of servers it does -- ergo, someone will always want to come to it for what it has, right? Yes and no. The difference between someone like Sun and, say, Microsoft (another legacy proprietary-offerings company) is that even Microsoft realizes that it's not irreplaceable anymore. It has been pushed, hard, by the presence of Linux in particular and open source in general, and it has started to respond in ways that show it takes the whole thing seriously and isn't about to get elbowed out.

One other thing that comes to mind: if Sun is doomed -- or at the very least in major trouble -- what will come of the open source projects that have come under its umbrella, such as OpenOffice or MySQL? The former already has a second home in the form of IBM's rebranded Lotus Symphony -- and even if IBM doesn't pick up on it, there are tons of other possible candidates to continue the project. Ditto MySQL, although nobody's going to be thrilled about a possible loss of project continuity if Sun chokes.

Whatever Sun does, it had better be fast. Shareholders are harsh mistresses.


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