Monday, August 04, 2008

Open Linux Elitists

There are all manner of Linux Elitists. There are distro elitists, window manger elitists, really really FLOSS elitists. There are Really-Damned-Small-Puppy-Peanut elitists. There are DIY Linux elitists. I, for one, fall into the Slackware distro elitist category. Slack and I go way back.

In fairness I can say that I have tried in the neighborhood of 30 different distros. I have looked so far afield as the BSD flavors and I have even touched Plan9. It took me just a minute be I was also able to lay hands on my copy of Sun Solaris(tm) Express. I believe, speaking of Linux, that I have been around the block at least once.

So after all of my wanderings I return to my Capistrano, my Slackware. This infatuation is not born on the sharp point of one like or dislike. Afterall, Linux is Linux, for the most part. I return first to the comfort of what I know. What is familiar to me. Then I return for what Slackware isn't - or should I say doesn't.

Slackware doesn't choose for me. Slack doesn't make up my mind for me. If there is something that I want from Slackware I am responsible for making it come to the surface. And here it is that I come to the crux of the elitist bisquit. Recently, perhaps in the past 18 months, it has become increasingly difficult to integrate certain software packages into what I consider the ultimate vanilla Linux distro, Slackware.

More and more I am finding some larger applications that are engineered for a specific distro. Or the program requires an essoteric set of libraries. Or it needs so-and-so's widget package. So I begin to play the dependency game. Find out what the program wants, go get and compile, then find out what the dependencies want, go get and compile ... then try to remember what was important about the original program. Very quickly the law of diminishing returns takes its toll.

Then there are other large applications suites that which are wholey self-sustained. OpenOffice as an example requires only that I rpm2tgz convert the distribution files and then installpkg them right into Slack. No dependencies, no drips, no runs, no errors. VMware is another example of arun-it-and-forget-it large application BUT the promise of their next version may negate that claim.

With regard to Linux elitists I would offer this cautionary note: complexity of implementation can be just as alienating as the prospect of proprietary software. If I cannot compile (with a minimum of dependencies) and run your sparkling new program or application then I simply walk away - no matter how important your contribution.

Yes, I am a Linux Elitist. I am a Slackware Snob. I will not give up a galloping stallion to change in mid-stream to a plodding donkey just so your software will work.


I am going to vote for Barack Obama.
I am William "Papa" Meloney and I endorse this message.

No comments:

Post a Comment

. . .