9:28in productionCh. 1 · The Launch/ 9:28 · ceiling 15 min
Software
Richard Stallman
Copyleft is not generosity — it’s copyright weaponised to make freedom non-negotiable.
Richard Stallman did not invent software, Unix, or open source. He invented copyleft: a legal construct that uses copyright law to guarantee four software freedoms. It works by attaching irrevocable conditions to distribution. It succeeded in sustaining the GNU toolchain and enabling Linux. It fails to constrain SaaS, firmware blobs, or patent thickets. It changed software licensing from permissive grant to reciprocal obligation. It is worth your time only if licence compliance directly affects your code’s deployment, maintenance, or liability.
The GNU Project was not an OS release — it was a declaration of intent to rebuild computing from free components.
2:53
The Mechanism
Copyleft isn’t anti-copyright — it’s copyright applied in reverse: to compel sharing, not restrict it.
4:09
The Licence
The GPL is not a moral statement — it’s a self-executing legal clause that triggers on distribution.
5:22
The Movement
The free software movement began the moment the GNU Project’s terms became enforceable — not when the first binary shipped.
Worth your time?
Yes. Study the whole thing.
4.5/ 5
What works
enforcing source availability
sustaining GNU toolchain adoption
binding derivative works to same terms
What does not
hardware
algorithms
physical instruments
Study it if
developers
legal counsel
open-source maintainers
Skip it if
end-users
hardware engineers
AI researchers
The written brief1 min read
What it is and the problem it solves
A legal mechanism — copyleft — that solves the problem of software freedom erosion by binding downstream users to the same rights they received.
How it works
Copyleft uses copyright law to require that derivative works remain free. It attaches licensing conditions to software distribution, mandating source code availability and permitting modification and redistribution only under identical terms.
What works
The GPL has enforced source availability across decades of Linux kernel development, GNU toolchain adoption, and embedded systems deployment. Its viral reciprocity has sustained public access to critical infrastructure code.
What does not
It does not prevent commercial use, restrict runtime behaviour, or govern hardware, algorithms, or network services. It does not apply to non-software works unless explicitly adapted, and it does not enforce attribution or patent grants by default.
What it changes
It redefined software ownership from exclusion to conditional sharing. It made freedom a legal invariant rather than a policy preference. It shifted the burden of preserving openness from community goodwill to licence enforcement.
Is it worth your time
Yes — if you write, distribute, or depend on software whose freedoms are legally enforceable. No — if your work operates entirely within proprietary ecosystems with no need for licence interoperability or source rights guarantees.