summaryrefslogtreecommitdiff
path: root/talermerchantdemos/blog/articles/zh/microsoft-verdict.html
blob: d12ccb8b07b2dbadb5620141e27a4faeab2aa9cf (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
<!--#set var="ENGLISH_PAGE" value="/philosophy/microsoft-verdict.en.html" -->

<!--#include virtual="/server/header.zh-cn.html" -->
<!-- Parent-Version: 1.96 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<!--#set var="TAGS" value="essays cultural evils" -->
<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->

<!-- This file is automatically generated by GNUnited Nations! -->
<title>关于对微软的判决 - GNU 工程 - 自由软件基金会</title>

<!--#include virtual="/philosophy/po/microsoft-verdict.translist" -->
<!--#include virtual="/server/banner.zh-cn.html" -->
<!--#include virtual="/philosophy/ph-breadcrumb.zh-cn.html" -->
<!--GNUN: OUT-OF-DATE NOTICE-->
<!--#include virtual="/server/top-addendum.zh-cn.html" -->
<div class="article reduced-width">
<h2>关于对微软的判决</h2>
<div class="thin"></div>

<p>
许多 <a href="/gnu/linux-and-gnu.html">GNU/Linux</a>
用户认为我们的系统是要和微软竞争。但是自由软件运动的目标是要解决一个宏大得多的问题:专有、非自由的软件让用户无助并禁止合作。微软是此类软件的最大开发者,但是众多其他公司对待用户自由是一样的糟糕;如果说它们没有套牢和微软一样多的用户,并不意味着它们没有尽力去做。</p>
<p>
由于微软只是问题的一部分,因此其在反垄断法上的挫败并不必然是自由软件的胜利。这个诉讼的结果是否帮到自由软件并推进用户自由依赖于法官对微软的具体惩治条款。</p>
<p>
如果惩治是让其他公司在提供专有、非自由软件上有竞争力,那么不会对自由世界有什么益处。能换成其他主子并不是自由。竞争可能会让他们的工作
&ldquo;更好&rdquo;,在狭隘的技术面上更好;然后我们和他们在技术上 &ldquo;竞争&rdquo;
就愈发困难。我们会继续为用户提供一件他们没有的东西&mdash;&mdash;自由&mdash;&mdash;珍爱自由的用户会因此继续选择自由软件。但是不把自由当回事的用户会出于方便来选择系统,他们就可能被诱惑到
&ldquo;经过改进的&rdquo; 专有系统阵营。</p>
<p>
把微软拆分成几个独立的公司也会给自由软件带来危险,因为这些小公司不再背负着公众谴责微软的负担,他们有可能比现在联合在一起的微软更适合对自由软件进行猛烈的攻击。</p>
<p>
我已经为此案件提出了 <a
href="/philosophy/microsoft-antitrust.html">建议的惩治条款</a>,这有助于自由软件和微软竞争:例如,要求微软公布所有接口文档,并只许用专利来防守,不得使用专利来攻击。这些条款会阻止微软使用这些武器对付我们的计划(据微软内部泄漏的
&ldquo;万圣节文档&rdquo; 所述,他们计划以此来阻挠 GNU/Linux 系统的开发)。</p>
<p>
当我们看到法官选择的条款之时,我们就会明了该案件对自由软件运动是利是弊。</p>
</div>

<div class="translators-notes">

<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
 </div>
</div>

<!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.zh-cn.html" -->
<div id="footer" role="contentinfo">
<div class="unprintable">

<p>请将对FSF&amp;GNU的一般询问发送到<a
href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>。还有一些其他联系FSF的<a
href="/contact/">方式</a>。关于链接错误和&rdquo;其他更正或建议&ldquo;请发信到<a
href="mailto:web-translators@gnu.org">&lt;web-translators@gnu.org&gt;</a>。</p>

<p>
<!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">

        &lt;web-translators@gnu.org&gt;</a>.</p>

        <p>For information on coordinating and contributing translations of
        our web pages, see <a
        href="/server/standards/README.translations.html">Translations
        README</a>. -->
我们尽最大努力来提供精准和高质量的翻译,但难免会存在错误和不足。如果您在这方面有评论或一般性的建议,请发送至 <a
href="mailto:web-translators@gnu.org">&lt;web-translators@gnu.org&gt;</a>。</p><p>关于进行协调与提交翻译的更多信息参见
<a href="/server/standards/README.translations.html">《译者指南》</a>。</p>
</div>

<!-- Regarding copyright, in general, standalone pages (as opposed to
     files generated as part of manuals) on the GNU web server should
     be under CC BY-ND 4.0.  Please do NOT change or remove this
     without talking with the webmasters or licensing team first.
     Please make sure the copyright date is consistent with the
     document.  For web pages, it is ok to list just the latest year the
     document was modified, or published.
     
     If you wish to list earlier years, that is ok too.
     Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
     years, as long as each year in the range is in fact a copyrightable
     year, i.e., a year in which the document was published (including
     being publicly visible on the web or in a revision control system).
     
     There is more detail about copyright years in the GNU Maintainers
     Information document, www.gnu.org/prep/maintain. -->
<p>Copyright &copy; 2000, 2021 Free Software Foundation, Inc.</p>

<p>本页面使用 <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative Commons
Attribution-NoDerivatives 4.0 International License</a> 授权。</p>

<!--#include virtual="/server/bottom-notes.zh-cn.html" -->
<div class="translators-credits">

<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
<b>翻译团队</b>:<a rel="team"
href="//savannah.gnu.org/projects/www-zh-cn/">&lt;CTT&gt;</a>,2022。</div>

<p class="unprintable"><!-- timestamp start -->
最后更新:

$Date: 2022/05/08 07:36:43 $

<!-- timestamp end -->
</p>
</div>
</div>
<!-- for class="inner", starts in the banner include -->
</body>
</html>