| Management number | 233488068 | Release Date | 2026/06/27 | List Price | US$7.93 | Model Number | 233488068 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
The history of open source is not a story of triumph. It is a cycle.Software begins as a shared commons. It becomes valuable. Commercial actors extract the value. The community resists, and the cycle begins again.From the RAND Corporation's code-sharing meetings in 1955 to the licence rebellions of 2021, the history of open source software follows a pattern so consistent it reads like a law: openness enables adoption, adoption attracts enclosure, enclosure provokes resistance. The cycle repeats. The stakes escalate.Free as in Theft traces this arc across seven decades — from Unix to Linux, from the browser wars to the cloud, from the mobile duopoly to the AI frontier. Twenty-three chapters, eight eras, three continents.Inside you will find:The 1956 consent decrees that accidentally created the software commonsWhy GitHub's acquisition was the most durable enclosure in the bookHow the fork fails when the resource is compute, not codeWhat "open" means when four nations claim sovereignty through the same standard This is a practitioner's history. Andreas Hamberger has spent thirty years deploying and governing open source systems across New Zealand's enterprise and public sector. He watched the pattern repeat from inside ICONZ in 1997, inside Novell in 2004, and inside the AI governance debates of 2025.The same pattern that played out over a decade for Unix is now repeating in months for AI. The question is not whether it is happening. The question is who will own it when it is done.The pattern is in the record. Read the record. Read more
| ISBN10 | 0473784556 |
|---|---|
| ISBN13 | 978-0473784553 |
| Language | English |
| Publisher | Te Pono |
| Dimensions | 6 x 0.92 x 9 inches |
| Item Weight | 1.38 pounds |
| Print length | 367 pages |
| Publication date | April 6, 2026 |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form