Commentary

Serdar Yegulalp
 

Invisible Linux: The Details

The other week I theorized about "Invisible Linux" -- what Linux would need to become to really make inroads on the desktop. Since making that post, I've been refining my ideas about what this would be and how it could be created. Read on for more.

The other week I theorized about "Invisible Linux" -- what Linux would need to become to really make inroads on the desktop. Since making that post, I've been refining my ideas about what this would be and how it could be created. Read on for more.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Invisible Linux would essentially do for Linux what Apple did with NeXTStep / BSD: take the open source core and wrap it in a layer that may not be open source but which is polished to a degree that makes it irresistible to end users. Such a package would consist of three things: a stable and dependable ABI/API layer for programmers; a professionally designed and use-tested interface for end users; and an organized deployment of all these things for the sake of administrators and commercial software creators.

The first and third could be accomplished any number of ways (pick a stable implementation of each and freeze it), but #2 -- the UI -- is really the toughest and most elusive of the bunch. Getting a UI right for a desktop OS is brutally difficult, and it's clear to me now that it just can't be done as an open-ended community effort. KDE and GNOME suffer from either designs that are good enough but not inspired, or too much design work that doesn't serve any real purpose except being "different" for its own sake.

To make Invisible Linux look good, there needs to be an actual design team with a designer on board -- a graphic artist whose job is to do nothing but create something that we would be happy to spend several hours a day looking at. And, frankly, such people cost money. With their talent, they could have their pick of projects, and I doubt they would work on something this all-consuming and detailed without asking for at least something back.

Everything I see here tells me Invisible Linux would need to be at least partly a commercial software project. One canard that keeps bubbling back to the surface is how any attempt to make Linux fly on the desktop will require the support of third-party, closed-source software makers. The problem is getting them to develop for a platform that commands so little marketshare -- and which is (in their perception) mainly used by people who choose not to pay for software in the first place. That's going to be a tough one to knock down.

In many ways, Linux is already a success, as I've mentioned before. It's been fairly revolutionary as a server platform; nobody needs to be brought back over this ground again. But it's going to remain fragmented on the desktop unless someone comes along, takes it as raw material, and fashions it into a form that even Linux's own creators couldn't imagine -- and does so by harnessing the twin powers of capital and singular design.

But given that Linux is meant to be thus shaped and bent, wouldn't they be happy about that?


InformationWeek has published an in-depth report on Windows 7. Download the report here (registration required).


Follow me and the rest of InformationWeek on Twitter.


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