Merge from emacs-24; up to 2012-05-08T14:11:47Z!monnier@iro.umontreal.ca
[bpt/emacs.git] / etc / WHY-FREE
CommitLineData
177c0ea7 1 Why Software Should Not Have Owners
a933dad1
DL
2
3 by Richard Stallman
4
5Digital information technology contributes to the world by making it
6easier to copy and modify information. Computers promise to make this
7easier for all of us.
8
9Not everyone wants it to be easier. The system of copyright gives
10software programs "owners", most of whom aim to withhold software's
11potential benefit from the rest of the public. They would like to be
12the only ones who can copy and modify the software that we use.
13
14The copyright system grew up with printing--a technology for mass
15production copying. Copyright fit in well with this technology
16because it restricted only the mass producers of copies. It did not
17take freedom away from readers of books. An ordinary reader, who did
18not own a printing press, could copy books only with pen and ink, and
19few readers were sued for that.
20
21Digital technology is more flexible than the printing press: when
22information has digital form, you can easily copy it to share it with
23others. This very flexibility makes a bad fit with a system like
24copyright. That's the reason for the increasingly nasty and draconian
25measures now used to enforce software copyright. Consider these four
26practices of the Software Publishers Association (SPA):
27
28* Massive propaganda saying it is wrong to disobey the owners
29to help your friend.
30
31* Solicitation for stool pigeons to inform on their coworkers and
32colleagues.
33
34* Raids (with police help) on offices and schools, in which people are
35told they must prove they are innocent of illegal copying.
36
37* Prosecution (by the US government, at the SPA's request) of people
38such as MIT's David LaMacchia, not for copying software (he is not
39accused of copying any), but merely for leaving copying facilities
40unguarded and failing to censor their use.
41
42All four practices resemble those used in the former Soviet Union,
43where every copying machine had a guard to prevent forbidden copying,
44and where individuals had to copy information secretly and pass it
45from hand to hand as "samizdat". There is of course a difference: the
46motive for information control in the Soviet Union was political; in
47the US the motive is profit. But it is the actions that affect us,
48not the motive. Any attempt to block the sharing of information, no
49matter why, leads to the same methods and the same harshness.
50
51Owners make several kinds of arguments for giving them the power
52to control how we use information:
53
54* Name calling.
55
56Owners use smear words such as "piracy" and "theft", as well as expert
57terminology such as "intellectual property" and "damage", to suggest a
58certain line of thinking to the public--a simplistic analogy between
59programs and physical objects.
60
61Our ideas and intuitions about property for material objects are about
62whether it is right to *take an object away* from someone else. They
63don't directly apply to *making a copy* of something. But the owners
64ask us to apply them anyway.
65
66* Exaggeration.
67
68Owners say that they suffer "harm" or "economic loss" when users copy
69programs themselves. But the copying has no direct effect on the
70owner, and it harms no one. The owner can lose only if the person who
71made the copy would otherwise have paid for one from the owner.
72
73A little thought shows that most such people would not have bought
74copies. Yet the owners compute their "losses" as if each and every
75one would have bought a copy. That is exaggeration--to put it kindly.
76
77* The law.
78
79Owners often describe the current state of the law, and the harsh
80penalties they can threaten us with. Implicit in this approach is the
81suggestion that today's law reflects an unquestionable view of
82morality--yet at the same time, we are urged to regard these penalties
83as facts of nature that can't be blamed on anyone.
84
85This line of persuasion isn't designed to stand up to critical
86thinking; it's intended to reinforce a habitual mental pathway.
87
88It's elemental that laws don't decide right and wrong. Every American
89should know that, forty years ago, it was against the law in many
90states for a black person to sit in the front of a bus; but only
91racists would say sitting there was wrong.
92
93* Natural rights.
94
95Authors often claim a special connection with programs they have
96written, and go on to assert that, as a result, their desires and
97interests concerning the program simply outweigh those of anyone
98else--or even those of the whole rest of the world. (Typically
99companies, not authors, hold the copyrights on software, but we are
100expected to ignore this discrepancy.)
101
102To those who propose this as an ethical axiom--the author is more
103important than you--I can only say that I, a notable software author
104myself, call it bunk.
105
106But people in general are only likely to feel any sympathy with the
107natural rights claims for two reasons.
108
109One reason is an overstretched analogy with material objects. When I
110cook spaghetti, I do object if someone else takes it and stops me from
111eating it. In this case, that person and I have the same material
112interests at stake, and it's a zero-sum game. The smallest
113distinction between us is enough to tip the ethical balance.
114
115But whether you run or change a program I wrote affects you directly
116and me only indirectly. Whether you give a copy to your friend
117affects you and your friend much more than it affects me. I shouldn't
118have the power to tell you not to do these things. No one should.
119
120The second reason is that people have been told that natural rights
121for authors is the accepted and unquestioned tradition of our society.
122
123As a matter of history, the opposite is true. The idea of natural
124rights of authors was proposed and decisively rejected when the US
125Constitution was drawn up. That's why the Constitution only *permits*
126a system of copyright and does not *require* one; that's why it says
127that copyright must be temporary. It also states that the purpose of
128copyright is to promote progress--not to reward authors. Copyright
129does reward authors somewhat, and publishers more, but that is
130intended as a means of modifying their behavior.
131
132The real established tradition of our society is that copyright cuts
133into the natural rights of the public--and that this can only be
134justified for the public's sake.
135
136* Economics.
137
138The final argument made for having owners of software is that this
139leads to production of more software.
140
141Unlike the others, this argument at least takes a legitimate approach
142to the subject. It is based on a valid goal--satisfying the users of
143software. And it is empirically clear that people will produce more of
144something if they are well paid for doing so.
145
146But the economic argument has a flaw: it is based on the assumption
147that the difference is only a matter of how much money we have to pay.
148It assumes that "production of software" is what we want, whether the
149software has owners or not.
150
151People readily accept this assumption because it accords with our
152experiences with material objects. Consider a sandwich, for instance.
153You might well be able to get an equivalent sandwich either free or
154for a price. If so, the amount you pay is the only difference.
155Whether or not you have to buy it, the sandwich has the same taste,
156the same nutritional value, and in either case you can only eat it
157once. Whether you get the sandwich from an owner or not cannot
158directly affect anything but the amount of money you have afterwards.
159
160This is true for any kind of material object--whether or not it has an
161owner does not directly affect what it *is*, or what you can do with
162it if you acquire it.
163
164But if a program has an owner, this very much affects what it is, and
165what you can do with a copy if you buy one. The difference is not
166just a matter of money. The system of owners of software encourages
167software owners to produce something--but not what society really
168needs. And it causes intangible ethical pollution that affects us
169all.
170
171What does society need? It needs information that is truly available
172to its citizens--for example, programs that people can read, fix,
173adapt, and improve, not just operate. But what software owners
174typically deliver is a black box that we can't study or change.
175
176Society also needs freedom. When a program has an owner, the users
177lose freedom to control part of their own lives.
178
179And above all society needs to encourage the spirit of voluntary
180cooperation in its citizens. When software owners tell us that
181helping our neighbors in a natural way is "piracy", they pollute our
182society's civic spirit.
183
184This is why we say that free software is a matter of freedom, not
185price.
186
187The economic argument for owners is erroneous, but the economic issue
188is real. Some people write useful software for the pleasure of
189writing it or for admiration and love; but if we want more software
190than those people write, we need to raise funds.
191
192For ten years now, free software developers have tried various methods
193of finding funds, with some success. There's no need to make anyone
194rich; the median US family income, around $35k, proves to be enough
195incentive for many jobs that are less satisfying than programming.
196
197For years, until a fellowship made it unnecessary, I made a living
198from custom enhancements of the free software I had written. Each
199enhancement was added to the standard released version and thus
200eventually became available to the general public. Clients paid me so
201that I would work on the enhancements they wanted, rather than on the
202features I would otherwise have considered highest priority.
203
204The Free Software Foundation, a tax-exempt charity for free software
205development, raises funds by selling CD-ROMs, tapes and manuals (all
206of which users are free to copy and change), as well as from
207donations. It now has a staff of five programmers, plus three
208employees who handle mail orders.
209
210Some free software developers make money by selling support services.
211Cygnus Support, with around 50 employees, estimates that about 15 per
212cent of its staff activity is free software development--a respectable
213percentage for a software company.
214
215Companies including Intel, Motorola, Texas Instruments and Analog
216Devices have combined to fund the continued development of the free
217GNU compiler for the language C. Meanwhile, the GNU compiler for the
218Ada language is being funded by the US Air Force, which believes this
219is the most cost-effective way to get a high quality compiler.
220
221All these examples are small; the free software movement is still
222small, and still young. But the example of listener-supported radio
223in this country shows it's possible to support a large activity
224without forcing each user to pay.
225
226As a computer user today, you may find yourself using a proprietary
227program. If your friend asks to make a copy, it would be wrong to
228refuse. Cooperation is more important than copyright. But
229underground, closet cooperation does not make for a good society. A
230person should aspire to live an upright life openly with pride, and
231this means saying "No" to proprietary software.
232
233You deserve to be able to cooperate openly and freely with other
234people who use software. You deserve to be able to learn how the
235software works, and to teach your students with it. You deserve to be
236able to hire your favorite programmer to fix it when it breaks.
237
238You deserve free software.
239
240
241Copyright 1994 Richard Stallman
242Verbatim copying and redistribution is permitted
243without royalty as long as this notice is preserved;
244alteration is not permitted.