Open-source software development is driven by global IT communities, and as is human, disagreements are inevitable. When multiple groups debate an issue, they form factions, pursue their own ideals, and compete to make their approach the common standard. And more than once, things can get quite. tense.
Therefore, even though your brand-new Linux installation may seem "tame," it's actually built upon fierce debates, even real "battles," to win users and influence. Below are three of the most important Linux battles that have helped shape the operating system that powers the world today.
'Holy War' revolves around the concept of freedom.
The first major conflict in the history of Linux and free software revolved around a seemingly simple question: What does 'freedom' truly mean?
This is where the familiar concept of 'free as it is, not free as it is, free beer' comes from. The Free Software Foundation (FSF), the organization behind the GPL license, views this as an ethical issue. According to them, source code must always be open, and if a commercial company writes additional code to improve or expand open-source software, they have an obligation to return that code to the community, in accordance with the original terms.
Meanwhile, the Open Source Initiative (OSI) takes a more pragmatic approach. Founded in 1998, OSI coined the term 'open source,' with the primary goal of encouraging businesses to adopt and use Free and Open Source Software (FOSS).
In practice, software licenses often allow both philosophies to coexist. However, things became controversial when the FSF released GPLv3, with provisions aimed at preventing the locking of GPL software in consumer devices, as exemplified by the case of TiVo. Clearly, very few companies would accept a license that would prevent them from controlling their devices, so GPLv3 was controversial from the start.
It's noteworthy that the Linux kernel remains loyal to GPLv2. Without a legal way to 'lock down' devices, millions of Linux devices would be in serious trouble. Regardless of which side you take, this is an ongoing debate, and it continues to influence Linux and the entire open-source software world to this day.
The desktop war never ends.
After all these years, the choice of desktop environment on Linux basically revolves around two names: KDE and GNOME. One important reason GNOME was created is because KDE uses the Qt framework, which initially raised concerns about copyright issues.
Today, Qt has adopted a dual licensing model, and KDE uses an open-source version, so KDE is essentially open-source software. However, when GNOME was first formed, this was still a major concern within the community.
In an alternate timeline, perhaps GNOME never existed and KDE would have been the only option. But in reality, this ideological divide created two large, parallel desktop ecosystems, and even today, divergences and controversies continue to emerge within each 'side'.
Systemd and the 'old generation': the init war divides the community.
To date, the 'init war' is perhaps the most dramatic conflict. The init system is the first program to run after the kernel is loaded, responsible for managing services, logging, devices, and the entire system boot process. Systemd was created with the ambition to unify and standardize all of this, aiming to overcome the problems inherent in outdated shell scripts and complex situations like race conditions.
It sounds perfectly logical, so where does the problem lie? In reality, many people don't oppose Systemd because it's inefficient, but because its design philosophy goes against the traditional Unix spirit. Systemd concentrates too much control into a single system.
When Debian, the foundation of countless other Linux distributions, decided to adopt systemd as the default, the community truly exploded. And true to the open-source spirit, the familiar solution was: fork it. The result was Devuan, a Debian fork that doesn't use systemd. However, unless you're staying up late debating the init system on forums, chances are you're using a systemd-based distro, and that has become modern Linux, whether you like it or not.
These three conflicts are just a fraction of the many that have shaped Linux. Interestingly, everything happened publicly—not just the source code, but also the debates and disagreements. With closed operating systems like Windows, similar conflicts exist, but they occur behind closed doors. When a product launches, everyone agrees… officially.
With Linux, you not only get to witness the entire 'behind-the-scenes' story, but you can also directly participate and contribute to shaping its future. Whether that's good or not depends on your perspective, but it's hard to deny that following these battles is truly fascinating.