taler-merchant-demos

Python-based Frontends for the Demonstration Web site
Log | Files | Refs | Submodules | README | LICENSE

technological-neutrality.html (6300B)


      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="essays upholding need" -->
      5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
      6 <title>Technological Neutrality and Free Software
      7 - GNU Project - Free Software Foundation</title>
      8  <!--#include virtual="/philosophy/po/technological-neutrality.translist" -->
      9 <!--#include virtual="/server/banner.html" -->
     10 <!--#include virtual="/philosophy/ph-breadcrumb.html" -->
     11 <!--GNUN: OUT-OF-DATE NOTICE-->
     12 <!--#include virtual="/server/top-addendum.html" -->
     13 <div class="article reduced-width">
     14 <h2>Technological Neutrality and Free Software</h2>
     15 
     16 <address class="byline">by <a href="https://www.stallman.org/">Richard
     17 Stallman</a></address>
     18 
     19 <p>Proprietary developers arguing against laws to move towards free
     20 software often claim this violates the principle of
     21 &ldquo;technological neutrality.&rdquo;  The conclusion is wrong, but
     22 where is the error?</p>
     23 
     24 <p>Technological neutrality is the principle that the state should not
     25 impose preferences for or against specific kinds of technology.  For
     26 example, there should not be a rule that specifies whether state
     27 agencies should use solid state memory or magnetic disks, or whether
     28 they should use GNU/Linux or BSD.  Rather, the agency should let
     29 bidders propose any acceptable technology as part of their solutions,
     30 and choose the best/cheapest offer by the usual rules.</p>
     31 
     32 <p>The principle of technological neutrality is valid, but it has
     33 limits.  Some kinds of technology are harmful; they may pollute air or
     34 water, encourage antibiotic resistance, abuse their users, abuse the
     35 workers that make them, or cause massive unemployment.  These should
     36 be taxed, regulated, discouraged, or even banned.</p>
     37 
     38 <p>The principle of technological neutrality applies only to purely
     39 technical decisions.  It is not &ldquo;ethical neutrality&rdquo; or
     40 &ldquo;social neutrality&rdquo;; it does not apply to decisions about
     41 ethical and social issues&mdash;such as the choice between free
     42 software and proprietary software.</p>
     43 
     44 <p>For instance, when the state adopts a policy of migrating to free
     45 software in order to restore the computing sovereignty of the country
     46 and lead the people towards freedom and cooperation, this isn't a
     47 technical preference.  This is an ethical, social and political
     48 policy, not a technological policy.  The state is not supposed to be
     49 neutral about maintaining the people's freedom or encouraging
     50 cooperation.  It is not supposed to be neutral about maintaining or
     51 recovering its sovereignty.</p>
     52 
     53 <p>It is the state's duty to insist that the software in its public
     54 agencies respect the computing sovereignty of the country, and that
     55 the software taught in its schools educate its students in freedom and
     56 cooperation.  The state must insist on free software, exclusively, in
     57 <a href="/philosophy/government-free-software.html">public
     58 agencies</a> and in <a href="/education/edu-schools.html">
     59 education</a>.  The state has the responsibility to maintain control
     60 of its computing, so it must not surrender that control to <a
     61 href="/philosophy/who-does-that-server-really-serve.html">Service as
     62 a Software Substitute</a>.  In addition, the <a
     63 href="/philosophy/surveillance-vs-democracy.html">state must not
     64 reveal to companies the personal data</a> that it maintains about
     65 citizens.</p>
     66 
     67 <p>When no ethical imperatives apply to a certain technical decision,
     68 it can be left to the domain of technological neutrality.</p>
     69 </div>
     70 
     71 </div><!-- for id="content", starts in the include above -->
     72 <!--#include virtual="/server/footer.html" -->
     73 <div id="footer" role="contentinfo">
     74 <div class="unprintable">
     75 
     76 <p>Please send general FSF &amp; GNU inquiries to
     77 <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
     78 There are also <a href="/contact/">other ways to contact</a>
     79 the FSF.  Broken links and other corrections or suggestions can be sent
     80 to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
     81 
     82 <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
     83         replace it with the translation of these two:
     84 
     85         We work hard and do our best to provide accurate, good quality
     86         translations.  However, we are not exempt from imperfection.
     87         Please send your comments and general suggestions in this regard
     88         to <a href="mailto:web-translators@gnu.org">
     89         &lt;web-translators@gnu.org&gt;</a>.</p>
     90 
     91         <p>For information on coordinating and contributing translations of
     92         our web pages, see <a
     93         href="/server/standards/README.translations.html">Translations
     94         README</a>. -->
     95 Please see the <a
     96 href="/server/standards/README.translations.html">Translations
     97 README</a> for information on coordinating and contributing translations
     98 of this article.</p>
     99 </div>
    100 
    101 <!-- Regarding copyright, in general, standalone pages (as opposed to
    102      files generated as part of manuals) on the GNU web server should
    103      be under CC BY-ND 4.0.  Please do NOT change or remove this
    104      without talking with the webmasters or licensing team first.
    105      Please make sure the copyright date is consistent with the
    106      document.  For web pages, it is ok to list just the latest year the
    107      document was modified, or published.
    108      
    109      If you wish to list earlier years, that is ok too.
    110      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
    111      years, as long as each year in the range is in fact a copyrightable
    112      year, i.e., a year in which the document was published (including
    113      being publicly visible on the web or in a revision control system).
    114      
    115      There is more detail about copyright years in the GNU Maintainers
    116      Information document, www.gnu.org/prep/maintain. -->
    117 
    118 <p>Copyright &copy; 2014, 2021 Free Software Foundation, Inc.</p>
    119 
    120 <p>This page is licensed under a <a rel="license"
    121 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
    122 Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
    123 
    124 <!--#include virtual="/server/bottom-notes.html" -->
    125 
    126 <p class="unprintable">Updated:
    127 <!-- timestamp start -->
    128 $Date: 2021/10/01 10:55:57 $
    129 <!-- timestamp end -->
    130 </p>
    131 </div>
    132 </div><!-- for class="inner", starts in the banner include -->
    133 </body>
    134 </html>