Commentary

Serdar Yegulalp
 

The 'Right' Linux

Any talk of Linux brings with it talk of what it will take to get Linux on the desktop in big numbers.  Much of the talk in this vein revolves around distribution X versus desktop Y, or something of that nature.  The real issue, though, may not be a particular distribution or package model, but the mind-set of the creators.

Any talk of Linux brings with it talk of what it will take to get Linux on the desktop in big numbers.  Much of the talk in this vein revolves around distribution X versus desktop Y, or something of that nature.  The real issue, though, may not be a particular distribution or package model, but the mind-set of the creators.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Rob Enderle, no stranger to the business, weighed in recently on what he thought would be needed to bring Linux to a broader audience.  His big point of comparison was Apple: Unix underpinnings (actually, BSD), but with a polished UI that is the envy of most everyone else.

Arguments about what constitute a good UI could go on forever.  The real issue here is how to produce one, and if we go by Apple's model, that means spending a great deal of money to hire, cultivate, and retain a development team capable of creating and polishing such a thing.

And so arises the question: Do you need to throw tons of money around to produce a good UI?  Or is it more about the development culture, where (as with Apple) the whole project is tightly managed from the inside out?

One associate of mine was of the opinion that good designers can be had cheap enough -- it's just that most FOSS development teams look down their noses at designers and don't see what they have to contribute as being just as important as the backend logic.  As he put it, the problem with FOSS UIs is that everyone thinks they're a UI designer, and most people -- most programmers, especially -- are just not.  They don't understand that what may be counterintuitive to them as a programmer is not counterintuitive to someone who is just trying to get through their day's work.

And so arises an even bigger question: Can you foster the right attitudes about programming vs. UI design without needing a closed-ended, autocratic environment to do it?  Or to put it another way: do we have to choose between a closed but reliable ecosystem, and an open but also scattershot one?

I'd like to think it's not a Hobson's choice between the two, and that an open ecosystem will yield more genuinely useful fruit than something with a one-way door.  But I also don't think it will happen spontaneously.  It will require people who can see Linux as a starting point and not a destination.


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