TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The Crushing Complexity of the GPL3

3 点作者 jwgarber5 个月前

1 comment

nabla95 个月前
The whole argument is silly.<p>The goodness of license is not determined how developers understand the text. The goodness of license is determined how it is interpreted in the courts. There are good websites who explain and different licenses to developers or help them to choose. If still not clear, ask software lawyer to explain details. <a href="https:&#x2F;&#x2F;choosealicense.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;choosealicense.com&#x2F;</a><p>Analogy with code. Code should be simple and easy to understand, but it&#x27;s more important to execute correctly, including all special cases. The microprocessor or interpreter is the &quot;court&quot; for code writing. The good license covers all cases and uses phraseology with well-defined meanings and existing interpretations. Legal contracts often have an ambiguity that is reduced when it is tested in court. The more it is tested, the better you know what it means.<p>GPL and MPL are very different types of copyleft. MPL is weak copyleft bound to individual files. It&#x27;s simple because it does simple things. If that&#x27;s enough go for it. But don&#x27;t complain when someone uses it according to the permissions the license gives.