Commentary

Serdar Yegulalp
 

Are There Really Too Many Linux Distros?

How are Linux distributions like digital cameras? It sounds like a joke on the order of, "What's the difference between a compulsive gambler and a revolving door?" (Answer: The revolving door knows when to stop.) But the more I've thought about it, the more I've realized that Linux distros are as varied as digital cameras, and for some of the same reasons.

How are Linux distributions like digital cameras? It sounds like a joke on the order of, "What's the difference between a compulsive gambler and a revolving door?" (Answer: The revolving door knows when to stop.) But the more I've thought about it, the more I've realized that Linux distros are as varied as digital cameras, and for some of the same reasons.

Every time I've picked up someone else's digital camera I've needed a quick walkthrough of how to shoot a picture with it -- but the fact that there's a lens, a viewfinder, and a shutter button generally doesn't change. Likewise, every time I've sat down to work with a new Linux distribution, I've had to re-accommodate myself to a different desktop or package manager, but the command line and the kernel are just about always the same.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Odds are there are enough similarities between this particular camera and almost all the others out there that there won't be much of a learning curve, but I still might need some hand-holding. Do I have to manually open the shutter? How does the autofocus work? Is there even an autofocus, or is it one of those cameras that's one meter to infinity? Will the flash strength peter out after only a few meters? Is there a real zoom or that useless "digital zoom"? If I'm just shooting one quick picture -- like if I'm just using someone else's camera to get a shot of them with a friend -- I generally don't need to know more than where the shutter / focus button is.

Likewise, if I sit down at a friend's Linux computer to check Gmail, odds are I won't have too much trouble finding where the Web browser is. But the more work I want to do with an unfamiliar distribution, the more work I have to do, period. That said, it's their Linux install, not mine, so I gotta deal.

Similarly, I don't hear a lot of complaints about how digital cameras are markedly unalike, because we expect that from cameras. They're different by design. Also, we tend to pick one camera at a time and stick with it. It's ours, and we chose that one and got to know it because it had the features we wanted. If someone else is using it, it's up to them to figure it out.

The reason I'm drawing this analogy is to address a question that other people have brought up from time to time. Would the best thing for Linux be a uniformity of presentation -- not just in the GUI, but everywhere else as well, including things like package management? It's tempting, but difficult to enforce (to say the least). The other question is: What, and who, is that uniformity for? If it's for broader adoption of Linux, that's one thing. But if it's to "correct" something that may not even really be broken in the first place, that's another.

Another counter-argument is that while it might speed adoption of Linux, whether among nontechnical users or relatively sophisticated ones, it may end up harming the very thing that has made Linux so remarkable: its diversity. Obviously it's impossible to make all incarnations of Linux perfectly uniform. But maybe it's also foolish to expect that they should be.

(For another viewpoint, see Too Many Linux Distros Makes For Open-Source Mess.)


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