My last two posts have focused on the Terminal, what it is and what it does. I believe that learning about AI requires we at least know what the Terminal is. Today I want to look at “Open Source” as no one will get far into AI before this phrase enters the conversation. So today I consider Free and Open Source software (FOSS) and Proprietary Software
In the modern digital age, the word “free” is one of the most heavily loaded terms in our vocabulary. We use it to describe everything from a zero-dollar app on our smartphones to the absence of constraints on our movement. This linguistic ambiguity can create a profound misunderstanding when discussing software.
When a developer offers a program for “free,” are they talking about the price tag, or are they talking about your rights?
To understand the future of digital sovereignty, one must navigate the divide between two fundamentally different worlds: Proprietary software and Free and Open Source Software (FOSS). The difference is not merely a matter of economics; it is the difference between “free as in beer” and “free as in speech.”
To grasp the essence of the software debate, we must first deconstruct the word “free.” In the realm of software, scholars and activists distinguish between two concepts: Gratis and Libre.
Gratis refers to cost. This is “free as in beer.” If you download a mobile game that costs nothing, it is gratis. It is a transaction—or a lack thereof—where no money changes hands. However, gratis tells you nothing about what you are allowed to do with that game. You can use it, but you cannot see how it works, you cannot change it, and you certainly cannot share it.
Libre refers to liberty. This is “free as in speech.” This is the core of the FOSS movement. When software is libre, you are granted the fundamental freedoms to run the program, study how it works, redistribute copies, and—most importantly—improve the code and release your improvements to the public.
When we say software is “free,” we are not promising you won’t pay a cent; we are promising that the software will not be your prison.
The history of computing was largely written by the proponents of proprietary software. This model is built on the concept of “intellectual property” as a walled garden. The code is a trade secret, a “black box” that the user can interact with but never penetrate.
In the 1980s and 90s, Microsoft became the poster child for this era. Under the leadership of Bill Gates, Microsoft’s strategy was centred on the dominance of Windows. By keeping the source code strictly confidential, Microsoft created a powerful ecosystem. The value lay in the “moat”—the fact that only Microsoft knew how the gears turned, making it impossible for competitors to replicate their work or for users to audit the system for bugs or backdoors. This led to immense profitability and the birth of the modern software industry, but it also birthed a period of intense “vendor lock-in,” where users became beholden to the whims, pricing, and update cycles of a single corporation.
Apple took a different, more curated approach to proprietary software. While Microsoft sought to dominate the desktop through ubiquity, Apple focused on the “Walled Garden.” Apple’s philosophy is one of controlled perfection. By controlling both the hardware and the closed-source software (macOS and iOS), they can ensure a seamless, highly optimised user experience. However, this “seamlessness” comes at the cost of autonomy. In Apple’s ecosystem, the user is a guest in a beautifully designed mansion, but they are not allowed to move the walls or inspect the plumbing.
As the giants built their walls, a rebellion was brewing. The seeds of the FOSS movement were planted in the mid-1980s by Richard Stallman, a programmer at MIT who became disillusioned by the encroaching proprietary nature of computing. Stallman realized that as software became “closed,” users were losing the ability to fix their own tools. He launched the GNU Project and the Free Software Foundation (FSF), driven by a moral imperative: software should be a tool for human liberty, not a tool for control.
However, the movement needed a kernel—a functional heart. In 1991, a Finnish student named Linus Torvalds released the Linux kernel. Unlike the proprietary kernels of the era, Torvalds released his code under a license that allowed anyone to study and modify it.
The marriage of Stallman’s philosophical framework (the GPL license) and Torvalds’ practical, high-performance kernel (Linux) created a tectonic shift. For the first time, a massive, global, decentralized community of developers could collaborate on a single, world-class operating system without a central corporation owning the rights. This was the birth of the “Open Source” era—a movement that proved that transparency could be more efficient than secrecy.
Today, the tension between these two models defines our digital infrastructure.
Security and Trust: The proprietary argument relies on “security through obscurity”—the idea that if no one can see the code, no one can find the holes. FOSS proponents argue for “Linus’s Law”: “Given enough eyeballs, all bugs are shallow.” Because the code is public, thousands of independent developers can audit it, finding and patching vulnerabilities far faster than a closed team at a single corporation.
The Cost of Entry vs. The Cost of Ownership: Proprietary software often has a low barrier to entry (the gratis model, such as subscription-based Software as a Service (SaaS)), but it carries the long-term cost of “renting” your digital life. FOSS may require a steeper learning curve or more initial configuration, but the “ownership” of the tool remains with the user.
The Prison Metaphor: The ultimate difference lies in “lock-in.” In a proprietary ecosystem, if a company decides to discontinue a feature, raise prices, or implement invasive tracking, the user has little recourse but to leave—which is often impossible due to file format incompatibilities. In the FOSS ecosystem, if you dislike the direction of a project, you can “fork” it. You can take the code, start a new branch, and build the version of the software you actually want to live in.
As we move further into an era of Artificial Intelligence and Cloud Computing, the distinction between gratis and libre becomes even more critical. As our lives migrate to the “cloud,” we are increasingly moving away from owning software and toward merely licensing access to it.
The debate between FOSS and proprietary software is not just a technical dispute between programmers; it is a civil rights issue for the digital age. It asks a fundamental question: Will the tools that shape our civilization be transparent, communal assets that empower the individual, or will they be opaque, proprietary instruments that command our compliance?
In the end, the choice is between being a user of a product, or a participant in a community. One offers a comfortable cage; the other offers a powerful, albeit complex, freedom.
Thank you to Gemma4:26b for your help in writting this article.