Skip to content
Back to the blog
  • Free Software
  • OpenSource
  • Tecnologia e Sociedade
  • Soberania Digital
  • Ética na Tecnologia
  • Forças Produtivas
  • Direitos Digitais

Free Software vs. Open Source

The History of the Split in the Movement

Have you ever wondered why some say "free software" and others say "open source," when both seem to describe the same type of publicly available code? This isn't just a difference in words. It's a political divide that has shaped the technology we use today. This post reveals how a digital emancipation movement was co-opted by corporate interests and what that means for you, the developer, now.

The Political Origins of Free Software (1983-1985)

The Collapse of the Sharing Community

Richard Stallman wasn't just a talented programmer at MIT. He was a leader of a political emancipation movement. When he founded the GNU Project in 1983 and the Free Software Foundation in 1985, he wasn't making a technical choice. He was responding politically to the enclosure of software that had previously been common in academia.

Stallman vividly describes the collapse of the MIT AI Lab's software sharing community. Until the early 1980s, programmers shared code freely. It was as natural a practice as sharing cooking recipes. But when Digital discontinued the PDP-10 series and the company Symbolics hired almost all the lab's hackers, this community crumbled.

Modern computers of the time, such as VAX or 68020, came with proprietary operating systems. You needed to sign a non-disclosure agreement (NDA) just to receive an executable copy. As Stallman recounts in his founding text:

"That meant that the first step in using a computer was to promise not to help your neighbor. A cooperative community was forbidden."

Stallman's Moral Choice

This wasn't a technical restriction. It was a political barrier. Proprietary software didn't arise naturally. It was imposed through legal and economic mechanisms that transformed common knowledge into private property.

Stallman then faced a moral choice. He could have joined the world of proprietary software, signing NDAs and developing closed-source software. He would have made money. But as he himself wrote, at the end of his career, he would look back on "years of building walls to divide people."

Instead, he chose to develop a free operating system. GNU stands for "GNU's Not Unix," a hacker joke that became a political project. The language of freedom (free as in freedom, not free as in free beer) has always been at the heart of the movement's narrative.

The Four Freedoms as Principles of Emancipation

The four freedoms of free software are not technical specifications. They are principles of digital emancipation:

  • Freedom 0: To run the program as you wish, for any purpose
  • Freedom 1: To study how the program works and modify it (requires access to the source code)
  • Freedom 2: To redistribute copies, free of charge or for a fee
  • Freedom 3: To distribute modified versions, benefiting the community

As the FSF explicitly states: "Using free software is making a political and ethical choice, asserting the right to learn and share what we learn with others."

This perspective was clearly anti-capitalist. Stallman saw proprietary software as a social problem of power and control, not of efficiency. The Free Software Foundation was created in 1985 as a non-profit organization to advocate for and educate about these principles.

"If I am not for myself, who will be? If I am only for myself, what am I? If not now, when?"

— Hillel (quoted by Richard Stallman in "The GNU Project")

Solid references confirm this political origin. Stallman himself wrote in "The GNU Project" that the decision was based on a spirit similar to that of Hillel.

The Four Freedoms: Ethical, Not Technical

It's crucial to understand that the four freedoms define free software as a matter of liberty, not price. This distinction isn't semantic. It's political.

Freedom vs. Price: A Political Distinction

Many misinterpret the term "free software" as thinking of free-of-charge software. But Stallman and the FSF have always emphasized: think of "free speech," not "free beer." The ambiguity of the word "free" in English has led to misunderstandings, but the FSF has never backed down from this terminology because it carries the correct political meaning.

Copyleft as a Guarantee of Freedoms

The four freedoms are inalienable. The mechanism that guarantees them is copyleft, implemented through the GNU General Public License (GPL). Copyleft uses copyright law, but inverts it to serve the opposite purpose: instead of restricting a program, it keeps the program free.

The central idea of copyleft is that everyone is granted permission to run, copy, modify, and distribute the program, but they are not allowed to add restrictions. Thus, the crucial freedoms are guaranteed to everyone who has a copy.

For copyleft to be effective, modified versions must also be free. This ensures that work based on the original is available to the community if it's published. When salaried programmers improve GNU software, copyleft prevents their employers from saying, "You can't share these changes because we're going to use them to make our proprietary version."

Stallman explains this need:

"The requirement that changes must be free is essential if we want to ensure freedom for every user of the program."

— Richard Stallman

The X Window System illustrates the problem that copyleft solves. Developed at MIT and released as free software with a permissive license, it was quickly adopted by companies that added it to their proprietary Unix systems, in binary form only, covered by the same non-disclosure agreement.

These copies of X were no more free software than Unix. The X developers didn't see this as a problem. Their goal wasn't freedom, it was "success," defined as "having many users." It didn't matter if those users had freedom.

This led to a paradoxical situation: if you judged based on the freedom provided by the distribution terms of the MIT release, X was free software. But if you measured the freedom of the average X user, you would have to say that it was proprietary software.

The GPL solves this by requiring that anything added to or combined with software under the GPL must also be free and under the GPL. It's a "hole big enough to sink a ship" that copyleft closes.

To understand more about the differences between licenses, see our post GPL vs MIT: Which License to Choose for Your Project.

Today, the FSF maintains that free software is an ethical imperative. As they state in their official definition: "Free software is a matter of liberty, not price. The criterion for a free manual is basically the same as for free software: it is a matter of giving all users certain freedoms."

The Netscape Case (1998): Victory or Co-option?

In January 1998, Netscape announced that it would make the Navigator code free and open source. This moment is often celebrated as a victory for free software. But was it really?

Netscape's motivation was commercial, not political. It was a defensive strategy against Microsoft, which dominated the browser market with Internet Explorer. Netscape saw the open source model as a way to compete, not an ideological conversion to the principles of Free Software.

This was the beginning of the corporate co-option of the movement. When companies realized that "open source" could be profitable, the discourse changed. There was no more talk of freedom, ethics, or emancipation. There was talk of "competitive advantages," "code quality," and "development efficiency."

Opening Netscape's code wasn't an act of generosity. It was a market maneuver. And that matters because it reveals the logic behind corporations' adoption of the open source model.

It's important to note that the creation of the term "Open Source" by Eric Raymond and Bruce Perens wasn't an intentional betrayal of Stallman's principles. It was a "necessity of the time" that, unfortunately, compromised the original principles of Free Software.

The material context explains this decision. In 1998, there were few developers working on free software. Projects needed continuous maintenance. The financial and intellectual contribution of companies with commercial and private interests was necessary at the time.

Raymond and Perens saw an opportunity: if they removed the rhetoric of "freedom" and "ethics," which scared executives, and focused on practical arguments, they could attract many more companies to contribute to open source software.

It worked. But at what cost?

Netscape wasn't advocating for digital emancipation. It was defending its market position. And when companies adopted "open source," they didn't adopt the political principles of Free Software. They adopted a development methodology that could increase their profits.

The Creation of the Term "Open Source"

The Marketing Strategy for Silicon Valley

In 1998, Eric Raymond, Bruce Perens, and others founded the Open Source Initiative (OSI) and coined the term "Open Source." The goal was explicit: to make free software more palatable to companies.

Raymond explicitly said that they needed to abandon the rhetoric of "freedom" so as not to scare Silicon Valley. The strategy was to focus on practical benefits: better quality software, more reliable, developed more efficiently through the "bazaar" model (many eyes, all bugs are shallow).

The Open Source Definition: Technical Criteria, Not Political

The Open Source Definition was derived from the Debian Free Software Guidelines, but with a crucial difference: it focused on the terms of the source code license, not on the user's freedoms.

The ten criteria of the OSD include free redistribution, availability of source code, permission for derivative works, non-discrimination against persons or fields of endeavor, and technology neutrality. These are technical criteria, not political.

Stallman criticizes this approach in "Why Open Source Misses the Point of Free Software":

"Some open source supporters considered the term a 'marketing campaign for free software', which would appeal to business executives by highlighting practical benefits of the software, without raising issues of right and wrong that they might not like to hear."

The Political Emptying of Language

The term "open source" quickly became associated with ideas and arguments based only on practical values: making powerful and reliable software. Most discussions about "open source" pay no attention to right and wrong, only to popularity and success.

This linguistic shift wasn't neutral. It was strategic. By removing the language of freedom, they also removed the politics. Software became a tool, not a movement.

Today, when someone says "I'm an open source developer" but never mentions freedom, that person is perpetuating the political emptying of the movement. It may not be intentional, but it's the effect of the linguistic choice.

Inevitable Bifurcation? Material Conditions and Corporate Contribution

The bifurcation between Free Software and Open Source was inevitable due to the material conditions of the time. It wasn't an abstract ideological choice. It was a response to the concrete conditions of software development in the 1990s.

There were far fewer developers then. Free software projects needed continuous maintenance. Without corporate contribution, many projects would die. Companies with commercial and private interests brought financial and intellectual resources necessary for the moment.

This is a materialist analysis, not a conspiratorial one. It's not about demonizing Raymond, Perens, or Netscape executives. It's about understanding how material conditions led to certain decisions.

Open Source had an ambiguous role. On the one hand, it allowed the growth of projects and the release of open source versions of private projects. Chromium is a clear example: open source code maintained by Google, used by millions, the basis of Chrome and other browsers.

But this release wasn't out of "goodness of heart." It was due to pressure from the community and the market. Google open sourced Chromium to compete with Firefox and Internet Explorer, to establish web standards that favored its services, to collect usage data through Chrome.

There's nothing wrong with companies using open source for their commercial interests. The problem is when we present this as an act of generosity or as "contribution to the community."

Companies have a profit motive. Expecting ethical behavior from them out of goodwill is naive. They act when it's in their financial interest. Sometimes this coincides with the interests of the free software community. Sometimes it doesn't.

The bifurcation was, therefore, a consequence of material conditions. It wasn't an individual betrayal. It was a structural adaptation that had political costs.

Stallman recognizes this complexity. He doesn't demonize individuals, but criticizes the philosophy:

"We in the free software movement don't think of the open source field as an enemy. The enemy is proprietary (nonfree) software. But we want people to know that we stand for freedom, so we don't accept being labeled as open source supporters."

Current Contradictions: AI, Cloud, and GitHub

The contradictions of 1998 haven't disappeared. They have intensified over time. Today we face problems that Stallman and his contemporaries couldn't have fully imagined.

Artificial Intelligence: Value Extraction on an Industrial Scale

GitHub Copilot and other AI models were trained on billions of lines of open source code without compensation to the original authors. The code that developers released under open source licenses is being used to train proprietary models that may replace their jobs.

This is a form of value extraction. AI companies use the digital commons (open source code) to create proprietary products that generate private profit. It's the enclosure of the digital commons in its most advanced form.

Cloud Computing: Monetization without Retribution

AWS and other cloud providers offer services based on open source software (Elasticsearch, Redis, MongoDB) without adequately giving back to the communities that maintain these projects. Companies use open source to build proprietary SaaS services.

This has led to a reaction: licenses like MongoDB's SSPL (Server Side Public License) and the BSL (Business Source License) try to prevent cloud providers from offering open source software as a service without contributing back. But these licenses aren't considered "open source" by the OSI.

GitHub: Corporate Centralization of Development

Microsoft, a historically proprietary software company, bought GitHub in 2018 for $7.5 billion. Today, Microsoft is one of the largest contributors on GitHub. Ironic? Perhaps. But it also reveals how open source has been fully integrated into the corporate business model.

GitHub has centralized open source development. Millions of developers use a proprietary platform to host open source code. Microsoft controls the infrastructure, the usage data, the relationships between developers.

A beginner developer today needs to understand this history if they want to identify with software as a political movement, not just as a commodity. Otherwise, they will be contributing to their own exploitation without realizing it.

But this isn't about forced political agitation. If this subject is important to you, you can use this foundation for your studies. You can learn by contributing to Free Software. You can review commits from Free Software projects to understand the technical and political decisions behind the code.

The CTA isn't "revolt now." It's study, understand, participate consciously. If you value freedom, act to maintain and defend it.

Language as a Battleground

The choice of words isn't neutral. "Free Software" emphasizes freedom (ethical, political). "Open Source" emphasizes methodology (practical, technical). This linguistic shift was strategic, and its effects persist today.

The change in language was both things: political betrayal AND necessary translation for the context of the 90s. This is a real contradiction, not a Manichean simplification.

Stallman argues that different words convey different ideas:

"'Free software.' 'Open source.' If it's the same software (or nearly so), does it matter which name you use? Yes, because different words convey different ideas."

He recognizes that the term "free software" is prone to misunderstandings (free as in liberty vs. free as in gratis), but argues that the solution is to educate, not abandon the term.

The adaptation of language may be necessary, but it must be a consensus of the Free Software community, not a corporate imposition. When Raymond and Perens created "open source," they didn't consult the community. They decided that the rhetoric of freedom was an obstacle and removed it.

Today, linguistic neutrality (terms like "FLOSS" or "FOSS") doesn't help. If you want to defend freedom, using a neutral term isn't the way. Defending freedom implies showing people your support for freedom.

Stallman concludes:

"Each time you say 'free software' instead of 'open source', you help our cause."

This doesn't mean that defenders of Free Software and Open Source can't work together on practical projects. They can and should. But they shouldn't confuse the philosophies.

Conclusion

Recognizing the roots and unfolding of this division isn't an exercise in nostalgia. It's a condition for understanding the tensions that define software development in the present.

What began as a digital autonomy project led by Stallman in the 1980s found an inflection point in 1998: the adoption of the term "Open Source" by the community. This transition responded to concrete needs for project sustainability, even if it diluted the original discourse of freedom.

Thirty years later, the dilemmas are worsening. AI models feed on public repositories without compensation. Cloud giants monetize community projects without proportional return. The main code hosting platform belongs to a corporation whose core has always been closed-source software.

For those now entering the field, understanding this trajectory is to distinguish between participating in a movement for technological autonomy or just producing digital commodities. The recent past illuminates the present: what seemed overcome has returned on an expanded scale.

How to proceed? Study the licenses before contributing. Examine commits from projects that truly preserve freedom. Question who benefits from your work. There's no pamphlet here: there's an invitation to grounded reflection and informed choice.

Every line you produce carries a political position, even when it claims neutrality. Writing code is building the world in which others will live. What world are you helping to create?

References

--- "

Matheus Mierzwa

AI Enablement Lead & Frontend Tech Lead

I write about what I build and lead in practice.