Non-free software carries with it an antisocial system that prohibits cooperation and community. You are typically unable to see the source code; you cannot tell what nasty tricks, or what foolish bugs, it might contain. If you don't like it, you are helpless to change it. Worst of all, you are forbidden to share it with anyone else. To prohibit sharing software is to cut the bonds of society.
Today we have a large community of users who run GNU, Linux and other free software. Thousands of people would like to extend this, and have adopted the goal of convincing more computer users to "use free software". But what does it mean to "use free software"? Does that mean escaping from proprietary software, or merely installing free programs alongside it? Are we aiming to lead people to freedom, or just introduce them to our work? In other words, are we working for freedom, or have we replaced that goal with the shallow goal of popularity?
It's easy to get in the habit of overlooking this distinction, because in many common situations it makes no difference. When you're trying to convince a person to try a free program, or to install the GNU/Linux operating system, either goal would lead to the same practical conduct. However, in other situations the two goals inspire very different actions.
For instance, what should we say when the non-free Invidious video driver, the non-free Prophecy database, or the non-free Indonesia language interpreter and libraries, is released in a version that runs on GNU/Linux? Should we thank the developers for this "support" for our system, or should we regard this non-free program like any other--as an attractive nuisance, a temptation to accept bondage, a problem to be solved?
If you take as your goal the increased popularity of certain free software, if you seek to convince more people to use some free programs some of the time, you might think those non-free program are helpful contributions to that goal. It is hard to dispute the claim that their availability helps make GNU/Linux more popular. If the widespread use of GNU or Linux is the ultimate goal of our community, we should logically applaud all applications that run on it, whether free or not.
But if our goal is freedom, that changes everything. Users cannot be free while using a non-free program. To free the citizens of cyberspace, we have to replace those non-free programs, not accept them. They are not contributions to our community, they are temptations to settle for continuing non-freedom.
There are two common motivations to develop a free program. One is that there is no program to do the job. Unfortunately, accepting the use of a non-free program eliminates that motivation. The other is the will to be free, which motivates people to write free replacements for non-free programs. In cases like these, that motive is the only one that can do the job. Simply by using a new and unfinished free replacement, before it technically compares with the non-free model, you can help encourage the free developers to persevere until it becomes superior.
Those non-free programs are not trivial. Developing free replacements for them will be a big job; it may take years. The work may need the help of future hackers, young people today, people yet to be inspired to join the work on free software. What can we do today to help convince other people, in the future, to maintain the necessary determination and persistance to finish this work?
The most effective way to strengthen our community for the future is to spread understanding of the value of freedom--to teach more people to recognize the moral unacceptability of non-free software. People who value freedom are, in the long term, its best and essential defense.
Copyright 2004 Richard Stallman
Verbatim copying and distribution of this entire article are
permitted world wide without royalty provided this notice is preserved.
Note: Comments are owned by the poster. We are not responsible for their content.
However, lots of additional contributions come from people who has a lot of flexibility on how they achieve their main job, and use that flexibility to help develop on the tools they use in their main job.
All the projects you mentioned are tools that are mostly used profesionally. If you work for a web hotel, contributing to apache comes naturally. Even if your job description is keeping the hotel running smoothly rather than developing software.
It is not worth much (being self-selected and all), but the <A HREF="http://www.infonomics.nl/FLOSS/report/" TITLE="infonomics.nl">FLOSS survey</a infonomics.nl> has approximately half the respondants being paid for their free software work.
The GNU General Public License encumbers Open Source Software with a schizoid and sociopathic personality disorder that renders it unable to work well with others, while blaming every other software producer for its failures. This is actually a side effect of a self-preservationist mentality that is a requirement for a business like Microsoft and other proprietary software vendors, but is unncessary baggage for a movement that should be aiming to provide users with a less hostile computing experience. The GPL was created to protect the software freedom of users by ensuring that the source code was always available and freely distributable, however it does little to protect the freedom of software users who care nothing about the availablity of the source code and more about usable software. Instead, it actually hinders the freedom of those users by forcing them to endure less than usable software for the sake of adhering to Richard Stallman's constant redefinition of freedom, which is forced cooperation rather than true freedom defended by its beneficiaries. As a result of these personality flaws, most open source software remains less than usable, garnering only the support of companies seeking self-preservation, when it should be willing and able to cooperate with the companies that are actually able to benefit projects with user interface research, as well as software and hardware support that is not constantly having to be reverse-engineered.
Who would benefit from a less socially bankrupt license? You. If you're a developer, you can stop chasing after less than open, yet de facto standards and cooperatate with software vendors that may not agree with your development strategy to create software that makes your software usable, predictable, reliable and interoperable for the people who really matter --- your users, who are your customers. You may sacrifice getting credit for your work as it is used in proprietary software, but if your goal is an ego stroke, your customers will suffer. If' you're a user, you will be able know that just because you switch to an open source platform, doesn't mean that you have to sacrifice your usablity on the RMS altar. If you're a computer manufacturer, you will know that you can sell a package with your computer that includes a mixture of open source and proprietary software -- depending on what works best for your customers, instead of having to compromise their experience for the sake of an anti-social political movement. And, if you're a GPL zealot, you can still install just open source software at all cost -- even if it causes you to be less productive and unable to work with others who don't share your beliefs.
however it does little to protect the freedom of software users who care nothing about the availablity of the source code and more about usable software
The GPL isn't designed to protect that. And where is it stated that "usable" software is a right? if they (or you) want "usable" software, you can open up your checkbook and support your favorite hard-to-use application's development team. Who knows? you may get your wishes (and your name in lights, or at least the acknowledgements).
Oh, wait...you want things gratis? ah, you're failing to distinguish between that term and libre.
<TT>
--
If I cound spell I'd have spelled it right in the first place!
</TT>
The Big Examples are of course companies like SuSE and Red Hat; but those are eclipsed by folks who are:
In fact, "Free Software" is simply an attempt to get the same sort of rights to software you buy that you do have if you buy a car or a brick. The fact that in order to do so you have to put a "you must publish the
lgpl
Posted by: Anonymous Coward on January 05, 2004 08:36 PMWhat the hell was the LGPL created for then? Try telling the people around Gnome that proprietary development should not be free.
#