Open Source & The Commons
The Gift That Runs the World
The software holding together the global financial system, your hospital's servers, and the app on your phone was probably written by volunteers who gave it away for free — and almost nobody finds this strange.
The Idea
Open source software operates on a logic that cuts against nearly everything we assume about how valuable things get made. The code is free to read, free to copy, free to modify. There is no wall around it. And yet this arrangement has produced some of the most robust, widely-deployed technology in human history — Linux, the kernel running most of the world's servers; Git, the version-control system underpinning almost all software development; OpenSSL, the encryption layer quietly protecting a vast share of internet traffic. The philosophical root of open source is not altruism, exactly. It is closer to a theory of knowledge: that complex systems improve faster when more minds can inspect and improve them. Linus's Law, named after Linux creator Linus Torvalds, puts it bluntly — 'given enough eyeballs, all bugs are shallow.' Secrecy does not make software safer; it just concentrates the risk in the hands of whoever holds the keys. But open source is also a political statement about ownership. Richard Stallman, the movement's more ideological godfather, framed it in terms of freedom — not free as in free coffee, but free as in free speech. The right to understand what your tools are doing, to fix them, to share what you learn. Code, in this view, is not just a product. It is infrastructure. And infrastructure, like roads or water systems, belongs most productively to everyone.
In the World
In 2014, a researcher named Neel Mehta discovered a catastrophic flaw in OpenSSL — a piece of software so ubiquitous it was estimated to protect roughly two-thirds of all encrypted web traffic at the time. The bug, quickly named Heartbleed, allowed an attacker to silently extract data from supposedly secure servers: passwords, private keys, the works. It had been sitting undetected in the codebase for two years. The reaction, in certain quarters, was triumphant: see, open source is dangerous. Anyone can read the code, which means attackers can too. But this misread the situation entirely. The bug was found precisely because the code was open. A closed, proprietary equivalent might have sat undiscovered for a decade, exploited quietly by whoever stumbled upon it first — most likely not a well-meaning researcher. Heartbleed also revealed something more uncomfortable: OpenSSL, despite underpinning a colossal share of global internet security, was being maintained by a tiny, underfunded team. The codebase that corporations were building billion-unit products on top of was essentially running on donated weekends. The response — a new initiative called the Core Infrastructure Initiative, funded by major tech companies — acknowledged what had always been true but rarely spoken: the commons had been quietly subsidising commercial software for years, and almost nobody had been paying attention.
Why It Matters
There is a version of this story that ends with a comforting conclusion: open source works, the community self-corrects, everything is fine. That would be too easy. What open source actually reveals is a recurring tension in how we build shared things. When something is free to use, the incentive to maintain it — to do the unglamorous, thankless work of patching and documenting and keeping the lights on — tends to fall on whoever cares most, which is often not the party extracting the most value from it. Economists call this the free-rider problem. The open source community calls it burnout. Knowing this should change how you look at the software stack underneath your daily life. It is not a neutral, self-sustaining utility. It is a layered gift economy, where some people give far more than they receive and the rest of us benefit without quite noticing. That is worth sitting with — not out of guilt, but because understanding the actual architecture of your world is the first step toward caring about it intelligently.
A Question to Ponder
If the infrastructure you depend on most is maintained by people doing it out of conviction rather than compensation, what does that tell you about which things society has decided are worth paying for — and which ones it has quietly decided to take for granted?
Get a new one of these every morning.
Start learning with Thinkable