why-programs-should-be-shared.html (5919B)
1 <!--#include virtual="/server/header.html" --> 2 <!-- Parent-Version: 1.96 --> 3 <!-- This page is derived from /server/standards/boilerplate.html --> 4 <!--#set var="TAGS" value="gnu-history" --> 5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" --> 6 <title>Why Programs Should be Shared 7 - GNU Project - Free Software Foundation</title> 8 <!--#include virtual="/gnu/po/why-programs-should-be-shared.translist" --> 9 <!--#include virtual="/server/banner.html" --> 10 <!--#include virtual="/gnu/gnu-breadcrumb.html" --> 11 <!--GNUN: OUT-OF-DATE NOTICE--> 12 <!--#include virtual="/server/top-addendum.html" --> 13 <div class="article reduced-width"> 14 <h2>Why Programs Should be Shared</h2> 15 16 <address class="byline">by <a href="https://www.stallman.org/">Richard 17 Stallman</a></address> 18 19 <div class="introduction"> 20 <p>Editor's note: This text was found in a file dated May 21 1983, though it is not clear whether it was written then or earlier. 22 In May 1983 Richard Stallman was privately considering plans to develop a 23 free operating system, but he may not yet have decided to make it a 24 Unix-like system rather than something like the MIT Lisp Machine.</p> 25 26 <p>He had not yet conceptually distinguished the two meanings of 27 “free”; this message is formulated in terms of gratis 28 copies, but take for granted that this means users also have freedom.</p> 29 </div> 30 <hr class="no-display" /> 31 32 <p>Five years ago one could take for granted that any useful program 33 written at SAIL, MIT, CMU, etc. would be shared. Since then, these 34 universities have started acting just like software houses—everything 35 useful will be sold for an arm and a leg (usually after being written 36 at gov't expense).</p> 37 38 <p>People find all sorts of excuses why it's harmful to give away 39 software. These supposed problems never bothered us back when we 40 <em>wanted</em> to share, and haven't affected EMACS, so I suspect they are 41 bogus.</p> 42 43 <p>For example, people say that companies will “steal” it 44 and sell it. If so, that would be no worse than Stanford selling it! 45 At least people would have the choice of getting a free copy. Users 46 want to buy maintained software? Then let people sell service 47 contracts—but give the software itself free.</p> 48 49 <p>I think I can dispose of any reasons you may think exist 50 for not sharing software. But more important is the reason 51 why we <em>should</em> share:</p> 52 53 <p>We would get more done with the same amount of work, if 54 artificial obstacles were removed. And we would feel 55 more in harmony with everyone else.</p> 56 57 <p>Sharing software is the form that scientific cooperation 58 takes in the field of computer science. Universities used 59 to defend the principle of scientific cooperation. 60 Is it right for them to throw it over for profit?</p> 61 62 <p>Should we let them?</p> 63 64 <p>Right now graduate students here are working on programming 65 projects that are specifically intended for sale. But if 66 we create a climate of opinion like that of five years ago, 67 the university wouldn't dare to do this. And if you start 68 sharing, other people might start sharing with you.</p> 69 70 <p>So let's start sharing again.</p> 71 </div> 72 73 </div><!-- for id="content", starts in the include above --> 74 <!--#include virtual="/server/footer.html" --> 75 <div id="footer" role="contentinfo"> 76 <div class="unprintable"> 77 78 <p>Please send general FSF & GNU inquiries to 79 <a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>. 80 There are also <a href="/contact/">other ways to contact</a> 81 the FSF. Broken links and other corrections or suggestions can be sent 82 to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p> 83 84 <p><!-- TRANSLATORS: Ignore the original text in this paragraph, 85 replace it with the translation of these two: 86 87 We work hard and do our best to provide accurate, good quality 88 translations. However, we are not exempt from imperfection. 89 Please send your comments and general suggestions in this regard 90 to <a href="mailto:web-translators@gnu.org"> 91 <web-translators@gnu.org></a>.</p> 92 93 <p>For information on coordinating and contributing translations of 94 our web pages, see <a 95 href="/server/standards/README.translations.html">Translations 96 README</a>. --> 97 Please see the <a 98 href="/server/standards/README.translations.html">Translations 99 README</a> for information on coordinating and contributing translations 100 of this article.</p> 101 </div> 102 103 <!-- Regarding copyright, in general, standalone pages (as opposed to 104 files generated as part of manuals) on the GNU web server should 105 be under CC BY-ND 4.0. Please do NOT change or remove this 106 without talking with the webmasters or licensing team first. 107 Please make sure the copyright date is consistent with the 108 document. For web pages, it is ok to list just the latest year the 109 document was modified, or published. 110 111 If you wish to list earlier years, that is ok too. 112 Either "2001, 2002, 2003" or "2001-2003" are ok for specifying 113 years, as long as each year in the range is in fact a copyrightable 114 year, i.e., a year in which the document was published (including 115 being publicly visible on the web or in a revision control system). 116 117 There is more detail about copyright years in the GNU Maintainers 118 Information document, www.gnu.org/prep/maintain. --> 119 120 <p>Copyright © 1983, 2015, 2021 Free Software Foundation, Inc.</p> 121 122 <p>This page is licensed under a <a rel="license" 123 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative 124 Commons Attribution-NoDerivatives 4.0 International License</a>.</p> 125 126 <!--#include virtual="/server/bottom-notes.html" --> 127 128 <p class="unprintable">Updated: 129 <!-- timestamp start --> 130 $Date: 2021/11/28 07:45:37 $ 131 <!-- timestamp end --> 132 </p> 133 </div> 134 </div><!-- for class="inner", starts in the banner include --> 135 </body> 136 </html>