taler-merchant-demos

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

microsoft-verdict.html (5916B)


      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 cultural evils" -->
      5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
      6 <title>On the Microsoft Verdict - GNU Project - Free Software Foundation</title>
      7 <!--#include virtual="/philosophy/po/microsoft-verdict.translist" -->
      8 <!--#include virtual="/server/banner.html" -->
      9 <!--#include virtual="/philosophy/ph-breadcrumb.html" -->
     10 <!--GNUN: OUT-OF-DATE NOTICE-->
     11 <!--#include virtual="/server/top-addendum.html" -->
     12 <div class="article reduced-width">
     13 <h2>On the Microsoft Verdict</h2>
     14 <div class="thin"></div>
     15 
     16 <p>
     17 Many 
     18 <a href="/gnu/linux-and-gnu.html">GNU/Linux</a>
     19 users think of the system as competition for Microsoft.
     20 But the Free Software Movement aims to solve a problem that is much
     21 bigger than Microsoft: proprietary, nonfree software, designed to
     22 keep users helpless and prohibit cooperation.  Microsoft is the
     23 largest developer of such software, but many other companies treat the
     24 users' freedom just as badly; if they have not shackled as many users
     25 as Microsoft, it is not for lack of trying.</p>
     26 <p>
     27 Since Microsoft is just a part of the problem, its defeat in the
     28 anti-trust lawsuit is not necessarily a victory for free software.
     29 Whether the outcome of this suit helps free software and promotes
     30 users' freedom depends of the specific remedies imposed on Microsoft
     31 by the judge.</p>
     32 <p>
     33 If the remedies are designed to enable other companies compete in
     34 offering proprietary, nonfree software, that will do the Free World
     35 no particular good.  Alternative possible masters is not freedom.  And
     36 competition could lead them to do a &ldquo;better&rdquo; job, better
     37 in a narrow technical sense; then it could be harder for us to
     38 &ldquo;compete&rdquo; with them technically.  We will continue to
     39 offer the user one thing those companies do
     40 not&mdash;freedom&mdash;and users who value freedom will continue to
     41 choose free software for that reason.  But users who do not value
     42 freedom, and choose a system based on mere convenience, might be
     43 enticed away to &ldquo;improved&rdquo; proprietary systems.</p>
     44 <p>
     45 Splitting Microsoft into separate companies could also endanger free
     46 software, because these smaller companies, no longer held in check by
     47 the public readiness to condemn Microsoft, might see fit to attack
     48 free software more harshly than the present unified Microsoft does.</p>
     49 <p>
     50 I've 
     51 <a href="/philosophy/microsoft-antitrust.html">proposed remedies</a>
     52 for this case that would help free software compete with Microsoft:
     53 for example, requiring Microsoft to publish documentation for all
     54 interfaces, and to use patents only for defense, not for aggression.
     55 These remedies would block the use of the weapons that Microsoft plans
     56 to use against us (according to the &ldquo;Halloween documents&rdquo;
     57 leaked from within Microsoft which spelled out how they plan to impede
     58 development of the GNU/Linux system).</p>
     59 <p>
     60 When we see what remedies the judge chooses, we will get an idea of
     61 whether the case has been helpful or harmful to the Free Software
     62 Movement.</p>
     63 </div>
     64 
     65 </div><!-- for id="content", starts in the include above -->
     66 
     67 <!--#include virtual="/server/footer.html" -->
     68 <div id="footer" role="contentinfo">
     69 <div class="unprintable">
     70 
     71 <p>Please send general FSF &amp; GNU inquiries to
     72 <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
     73 There are also <a href="/contact/">other ways to contact</a>
     74 the FSF.  Broken links and other corrections or suggestions can be sent
     75 to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
     76 
     77 <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
     78         replace it with the translation of these two:
     79 
     80         We work hard and do our best to provide accurate, good quality
     81         translations.  However, we are not exempt from imperfection.
     82         Please send your comments and general suggestions in this regard
     83         to <a href="mailto:web-translators@gnu.org">
     84         &lt;web-translators@gnu.org&gt;</a>.</p>
     85 
     86         <p>For information on coordinating and contributing translations of
     87         our web pages, see <a
     88         href="/server/standards/README.translations.html">Translations
     89         README</a>. -->
     90 Please see the <a
     91 href="/server/standards/README.translations.html">Translations
     92 README</a> for information on coordinating and contributing translations
     93 of this article.</p>
     94 </div>
     95 
     96 <!-- Regarding copyright, in general, standalone pages (as opposed to
     97      files generated as part of manuals) on the GNU web server should
     98      be under CC BY-ND 4.0.  Please do NOT change or remove this
     99      without talking with the webmasters or licensing team first.
    100      Please make sure the copyright date is consistent with the
    101      document.  For web pages, it is ok to list just the latest year the
    102      document was modified, or published.
    103      
    104      If you wish to list earlier years, that is ok too.
    105      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
    106      years, as long as each year in the range is in fact a copyrightable
    107      year, i.e., a year in which the document was published (including
    108      being publicly visible on the web or in a revision control system).
    109      
    110      There is more detail about copyright years in the GNU Maintainers
    111      Information document, www.gnu.org/prep/maintain. -->
    112 
    113 <p>Copyright &copy; 2000, 2021 Free Software Foundation, Inc.</p>
    114 
    115 <p>This page is licensed under a <a rel="license"
    116 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
    117 Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
    118 
    119 <!--#include virtual="/server/bottom-notes.html" -->
    120 
    121 <p class="unprintable">Updated:
    122 <!-- timestamp start -->
    123 $Date: 2021/10/01 17:02:54 $
    124 <!-- timestamp end -->
    125 </p>
    126 </div>
    127 </div><!-- for class="inner", starts in the banner include -->
    128 </body>
    129 </html>