- Open Source
- Tecnologia e Sociedade
- Forças Produtivas
- Futuro do Trabalho
- Economia de Plataforma
- Ética na Tecnologia
GPL vs MIT
Choosing a License is a Political Act
When you choose a license for your software, you're making a decision that goes far beyond technical convenience. You're defining who controls the code you write, who benefits from it, and what kind of digital commons we're collectively building. GPL and MIT aren't just different legal texts: they're distinct political projects for the future of technology.
What Copyleft Is and Why It Matters
To understand the political difference between GPL and MIT, we first need to understand the concept of copyleft. Contrary to what the name might suggest, copyleft isn't the opposite of copyright. It's a legal technique that uses copyright laws to guarantee freedom, not restriction.
The Free Software Foundation defines four essential freedoms that all free software must guarantee: the freedom to use the software for any purpose, the freedom to study and modify the code, the freedom to share copies, and the freedom to distribute modified versions. When a program offers all these freedoms, we call it free software.
Copyleft is the mechanism that ensures these freedoms are preserved in all derived versions. When you modify software under copyleft and distribute your version, you must do so under the same terms. This creates a protected digital commons: a common good that can't be enclosed by private interests.
The Four Fundamental Freedoms
Freedom 0: Use the software for any purpose
Freedom 1: Study how the software works and modify it
Freedom 2: Share copies with other people
Freedom 3: Distribute modified versions to benefit the community
According to Brett Smith of the GNU Project: "When a program offers users all these freedoms, we call it free software. Developers who write software can release it under the terms of the GNU GPL. When they do that, it will be free software, and it will remain free software, no matter who changes or distributes the program."
GPL: Defending the Digital Commons Against Enclosure
The GNU General Public License (GPL) is the most widely used copyleft license. Created by Richard Stallman in 1989, its most recent version (GPLv3) was published on June 29, 2007, after 18 months of public consultation with thousands of comments.
The GPL operates as a shield against the enclosure of the digital commons. When a company uses GPL code in its product and distributes that product, it must open-source the modifications. This prevents the commons from being transformed into private property without reciprocation.
The Linux kernel is the most emblematic example. Licensed under GPL v2 since 1992, it remains free and open to this day. Any distributed modification must be open-sourced under the same terms. This mechanism has created one of humanity's largest digital commons: 96.3% of web servers run GNU/Linux, according to W3Techs data from 2024.
GPL v3 Protections Against Modern Threats
GPLv3 was updated to protect copyleft against three contemporary threats:
Tivoization: Devices that run GPL software but prevent user modifications. GPLv3 requires distributors to provide all the information needed to install modified software on the device.
Anti-circumvention laws: Laws like the DMCA criminalize breaking DRM. GPLv3 states that the covered software doesn't count as an effective "protection" technology measure, preserving your right to write code that bypasses DRM.
Discriminatory patent agreements: When someone distributes GPLv3 software, they must provide all recipients with any necessary patent licenses. If a licensee tries to sue users for patent infringement, their license is terminated.
As Smith writes: "We updated the GPL to protect your copyleft from being undermined by legal or technological developments."
MIT and Apache: Individual Freedom or Open Door to Appropriation?
The MIT and Apache 2.0 licenses belong to the category of permissive licenses. They grant broad freedoms: you can use, modify, distribute, and even incorporate the code into proprietary software. The only typical requirement is to preserve the original copyright notice.
From the perspective of the developer's individual freedom, these licenses are maximal. You can do almost anything with the code. But from the perspective of the digital commons, they represent a structural vulnerability: anyone can take the code, modify it, close it, and sell it as a proprietary product.
The React Case: When a Permissive License Allows Unilateral Change
In 2017, Facebook announced that it would change React's license from MIT to BSD+Patents. This new license included a clause that allowed Facebook to revoke patent rights if you sued the company for any reason. The community reacted with alarm. Projects like WordPress and Automattic declared that they could no longer use React.
In 2018, after intense pressure, Facebook reverted to MIT. But the damage was done: the community learned that permissive licenses allow unilateral changes that can harm those who depend on the code. With copyleft, this wouldn't be possible: the terms are locked to protect the commons.
Structural Comparison
According to GitHub Choose a License, the fundamental difference is in the "Same license" column:
GPL: Modifications must be released under the same license (copyleft)
MIT/Apache: Modifications can be released under any license, including proprietary
Apache 2.0 has advantages over MIT: it includes an explicit patent grant and is compatible with GPLv3. But it maintains the same structural problem: it doesn't protect the commons against enclosure.
Real Cases: Linux (GPL), React (MIT), Git (GPL)
To understand the practical implications, let's analyze three emblematic cases:
Linux: Copyleft Keeps Critical Infrastructure Free
The Linux kernel, under GPL since 1992, is the proof of concept of copyleft on a global scale. No vendor has managed to close the kernel. Any company that wants to use Linux in its product must open-source the kernel modifications. This has created a level playing field where even small companies can compete using the same infrastructure as tech giants.
React: Permissive Freedom with Risk of Co-option
React, under the MIT license, has become the world's most popular front-end library. But the BSD+Patents episode revealed the fragility of the model: a single company controls the license and can change the terms unilaterally. The community had to mobilize to reverse the decision: a political cost that wouldn't exist with copyleft.
Git: GPL Ensures Development Tool Remains Free
Git, created by Linus Torvalds in 2005, is licensed under GPL v2. This means that any distributed modification must be open-sourced. Companies like GitHub, GitLab, and Bitbucket can offer commercial services on top of Git, but they can't close the tool itself. The commons remains accessible to all developers.
What Political Project Does Your License Support?
We've arrived at the central question: when choosing a license for your project, what world are you helping to build?
Choose GPL if You Believe In:
Defense of the digital commons: You want your code and all improvements to remain accessible to everyone, indefinitely
Reciprocity: Those who benefit from your work should contribute back
Protection against enclosure: Companies shouldn't be able to take your work, close it, and sell it without open-sourcing their modifications
Solidarity among developers: Building common goods that protect all contributors
Choose MIT/Apache if You Believe In:
Maximum adoption: You prioritize getting as many people as possible to use your code, even in proprietary software
Individual freedom of the developer: Each person should be able to do whatever they want with your code
Corporate pragmatism: Companies can contribute without open-sourcing their proprietary code
Trust in social norms: You believe the community will push back against abuses, even without legal protection
There's no universal answer. But it's essential to recognize that a license is politics materialized in code. Your choice has real consequences for the type of technological ecosystem we're building.
Alternatives and Paths: AGPL, Emerging Licenses
For developers looking to further strengthen copyleft, there are alternatives:
AGPL v3: Closing the SaaS Gap
The GNU Affero GPL v3 extends copyleft to software running on network servers. Under traditional GPL, if you run modified software on a server without distributing binaries, you don't have to open-source the code. AGPL closes this gap: users who interact with the software via the network have the right to receive the source code.
This is crucial in the SaaS era. Without AGPL, companies like Amazon or Google can take free software, modify it, offer it as a closed service, and not contribute back. With AGPL, they must open-source the modifications.
Emerging Anti-Capitalist Licenses
New licenses are emerging to address limitations of traditional open source:
License for Oppressive Purposes: Prohibits use by police, military, or surveillance forces
Cooperative Non-Violent Public License: Requires companies to pay for commercial use, reverting to cooperatives
Hippocratic License: Based on the Universal Declaration of Human Rights, prohibits violations
These licenses are controversial: the OSI doesn't consider them "open source" because they restrict fields of activity. But they represent an important critique: political neutrality is illusory. Permissive licenses are also political: they simply favor capitalist appropriation.
Conclusion: Your License Is Your Manifesto
We've reached the end of this analysis. What have we learned?
First, that GPL and MIT aren't equivalent. They represent distinct philosophies about property, commons, and reciprocity. GPL uses copyleft to protect the digital commons against enclosure. MIT prioritizes individual freedom and maximum adoption, even at the expense of the commons.
Second, that a license is political. There's no neutral choice. By licensing your code, you're taking a position on what kind of technological ecosystem you want to inhabit.
Third, that the React case demonstrated the vulnerability of permissive licenses. A company can change the terms unilaterally, and the community has little recourse. Copyleft locks the terms to protect all participants.
As developers, we have a concrete choice: to be mere digital executors or active builders of a more equitable future. The code we write today is the world we'll live in tomorrow.
Your license is your manifesto. What world are you coding?