Which should come first, the Chicken or the Egg?

I have noticed several people debating about whether they should support Linux applications that are not open source. Some of these people believe that the best way to promote open source adoption is to only use open source applications and to reject everything else. The problem with this method is that the market share of desktop Linux users is so small that they have very little influence on the direction of the software industry. They can hold their breath until they turn blue, but it is not going to change anything.

Using the most recent statistic I could find, only 2.8% of desktops were running Linux in 2003. I am sure that the Linux desktop market is growing fast, and that the percentage is now much higher than 2.8%. Even so, it is obvious that Linux desktops are a small minority of the desktop market. The fact that most software companies do not even release a version of their software for Linux proves this fact. Most software is created only for Microsoft Windows, and if the company has enough resources they may also port it to Mac OS X.

In my opinion, the chicken (which is user-friendly Linux) should come before the egg (which is completely open source Linux). This means that Flash, Java, hardware drivers, multimedia codecs (if legal) and other popular closed-source applications should be installed by default. If there is a high-quality open source alternative to the closed source application, then we should always go with that alternative. However, if there is no open source equivalent then the software should be included by default (assuming the licensing permits this).

For example, if a popular website uses Flash, then a new Linux user cannot participate in that site without first installing Flash. If that user is trying Linux for the first time, they may not spend anymore time trying to get Flash working, and we will have added another voice to the "Linux is hard" mentality.

Do I consider this a surrender in the battle against proprietary software and DRM? Definitely not! To put it military terms, my plan can be considered a controlled withdrawal in order to join with reinforcements. Once we have sufficient numbers, we can prepare for the next assault. Currently, Linux desktop users just don't have the leverage to move the software industry. Once there is a sizable piece of the desktop market running Linux, we can begin to cut out the non-open systems and replace them with open source replacements.

Please leave a comment to explain why you agree or disagree with this position.

Comments

  1. Anonymous10/25/2006 4:35 PM

    It definitely is a difficult position to be in and probably no easy solution to it all.

    I think part of what you're suggesting is being done with easyUbuntu & AutoMatix. This helps new users install the "hard stuff".

    Why don't we just team up and write open alternatives to these problems? :) Of course that would entail some intensive learning on my part but open alternatives would be the best solution.

    ReplyDelete
  2. Anonymous10/25/2006 4:41 PM

    I agree, and I disagree. First, where I agree.

    I agree that the new Linux user should not be presented with an entirely 100% open distro, like Debian. As you clearly pointed out, this presents to the user configurations, install headaches and troubleshooting woes. The "Linux is too hard" mentality is very real. As such, a new user to Linux should be pointed to Ubuntu, SuSE or Fedora Core where non-free applications and drivers are installed, or readily available.

    However, I disagree with your point on leveraging the market. Linux is in the position to leverage what applications are to be installed, and what a user wants. Will this have an impact outside of Linux? Windows or otherwise? No, but internally, it makes major waves. But even then, we are seeing the end of shareware and freeware apps in favor of open soource and free software *outside* the Linux community. It may not be playing on the corporate level, but it is playing nonetheless.

    I come from the standpoint that I only want to use free software, and Linux and GNU apps bring that option to me fairly easily. But I am experienced, and don't worry about the headache or troubleshooting that may lie ahead.

    Good post!

    ReplyDelete
  3. Anonymous1/19/2007 12:05 PM

    Your ideas presuppose that popularity is more important than freedom.

    You have chosen GNU/Linux for reasons not shared by the free-software community.

    ReplyDelete
  4. Anonymous11/14/2007 10:14 PM

    Do you want to find out more about Ukraine! Visit Ukraine guide!

    ReplyDelete

Post a Comment

Popular posts from this blog

Using the Cisco console in Linux

Image
Introduction People who work with Cisco network equipment need to be able to connect to the console port on their devices. In Windows, you can simply fire up HyperTerminal to get basic access to your devices. If you are using Linux, then you need to know how this can be done with an application called Minicom . Hardware First, you are going to need a Cisco console cable , a Cisco device, and a computer. If your computer has a serial port , then you can use the standard console cable that comes with every Cisco device. If you do not have a serial port (like most new laptops), then you need to purchase a USB to Serial adapter that supports Linux. This device will allow you to use the standard Cisco cable, which has a serial port on one end. Install Minicom You can easily install Minicom by using "System > Administration > Synaptic Package Manager". Search for "minicom" and choose to install the package. Click "Apply" and Minicom should be insta...
Read more

Linux NIC teaming recommendations

Image
Introduction In my job as a network engineer, I am constantly looking for ways to increase the availability of the network. This is especially true in the data center, where services are expected to always be available. One of the ways to increase the network availability of a server is by using multiple network interfaces. This technique has many different names, but I am just going to call it NIC teaming. Purpose of NIC Teaming NIC teaming increases network availability by removing single-points-of-failure (SPOF). These SPOFs are components that will cause a service outage if they become unavailable. If we consider a single network connection from your server to your switch, we can identify quite a few SPOFs: Server NIC failure Network cable failure (such as being cut or unplugged) Network switch failure (such as a planned firmware upgrade or unplanned outage) Methods of NIC Teaming The reason I am writing this blog is to help people understand the different options for NIC team...
Read more

What it takes to make Ubuntu ready for use

I recently installed Ubuntu 6.10 on a new PC at work. In this post I will document all the steps I had to perform to get it ready for everyday use. Each step is assigned a level of difficulty, which I define below: Very Easy Step can be completed without using the command prompt Intuitive to complete Easy Step can be completed without using the command prompt May require searching to find the right place to make the change Medium Requires a single command to be entered at the command prompt Requires searching internet resources to find the solution Hard Requires multiple commands to be entered at the command prompt Requires searching internet resources to find the solution Very Hard Requires multiple commands to be entered at the command prompt Requires searching internet resources to find the solution Requires the user to manually edit a configuration file These criteria are quite strict, because I believe that using an operating system should be intuitive, and not require any spec...
Read more