Linux is a Religion

Watching a digital crusade unfold in real-time on a Lemmy forum a few days ago, I was struck by a terrifying realisation. Dozens of users were locked in a fierce, polite, yet utterly unyielding holy war, each attempting to convert the heathens to their preferred Linux distribution. The rhetoric was indistinguishable from 16th-century theological debates, just heavily seasoned with acronyms. Unable to resist the gravitational pull of my own ego, I dropped a comment noting that I use Arch–a statement that effectively marks me as a fundamentalist. Seven people starred it. The dopamine hit was immediate, and deeply shameful.

There is a unique kind of dread that creeps up on you when you have spent two decades walking the earth as a committed atheist, viewing faith communities with the polite, anthropological distance of someone who considers theological devotion a cognitive defect, only to wake up one morning and realise you have accidentally joined a cult. I have become doctrinaire. I am devotional. I become quietly, irrationally furious when I see someone using apt instead of pacman. I have stumbled backward into the Linux, open-source, and privacy ecosystem and discovered a complete, all-encompassing theological system to fawn over.

Calling a subculture a “religion” is usually just a lazy linguistic shortcut to describe people who care a little too much about CrossFit or veganism. But a true religion does specific, heavy lifting for the human psyche. It provides a cosmology: an account of how the universe is structured and the foundational values holding it together. It produces orthodoxy, aggressively policing the boundary between correct belief and heresy. It generates an eschatology–a prophetic vision of how the world will ultimately end. It relies on highly specific rituals to mark the initiate against the uninitiated. Finally, it reproduces itself through conversion experiences that believers inevitably describe as “seeing the light.”

The Linux community executes every single one of these functions with terrifying, structural precision.

Every religion requires a Genesis myth and a pantheon of prophets. Our foundational cosmology is the free software philosophy, and like all cosmologies worth dying for, it is a moral position disguised as a technical one. In the beginning, the code was closed, and darkness was upon the face of the mainframe. Then came Richard Stallman.

Stallman did not launch the GNU Project in 1983 because he crunched the numbers and calculated that open-source collaboration would yield fewer bugs. He launched it because he experienced a profound moral revulsion at the idea of proprietary software. To Stallman, a world where humans could not read, modify, and share the tools they depended on was a world where human autonomy had been fatally violated. He once wrote that he could have amused himself writing code for money, but knew that at the end of his career, he would look back on “years of building walls to divide people.” That is pure, unadulterated Old Testament prophet energy. Stallman views proprietary software the way an exorcist views a demon. To him, the General Public License (GPL) is an unbreakable covenant holding the forces of corporate enclosure at bay. “Free as in speech, not as in beer.” That distinction is the rock upon which the church is built.

Then came Linus Torvalds, the architect of the kernel itself. Torvalds is the New Testament pragmatist. He does not share Stallman’s rigid theology, once famously quipping, “Talk is cheap. Show me the code.” Torvalds is interested in what actually works, what compiles, and what scales, rather than maintaining absolute doctrinal purity.

The tension between the Stallmanite moralists and the Torvalds pragmatists is the defining schism of the ecosystem. It is a disagreement over the fundamental nature of the shared project: What are we building this for? Who does it serve? What compromises will condemn our souls to the corporate abyss? Consequently, every single Linux distribution is forced to take a position in this theological landscape.

Debian is the ancient orthodox church. Its commitment to free software purity is absolute. The installation is archaic, the packages are old, and the aesthetic is unforgiving, but it is ideologically flawless. Debian’s willingness to make your life difficult in exchange for ideological consistency is a pure confession of faith.

Ubuntu is the megachurch. It has the fog machines, the coffee shop in the lobby, and the charismatic pastor wearing trainers. Ubuntu looked at the masses and decided that the church had to grow, even if it meant shipping proprietary drivers and pushing Snap packages onto the congregation. In doctrinal terms, Ubuntu made concessions to the secular world, making an easy path available–a move the orthodox view as an unforgivable temptation.

Rocky Linux and the broader Red Hat Enterprise ecosystem sit in the Benedictine tradition. They are the enterprise monks: conservative, stable, and deeply uninterested in whatever shiny new toy the desktop users are arguing about. They patch what is known, certify what is tested, and serve massive financial institutions whose only prayer is five nines of uptime. I run Rocky in an Incus virtual machine right now while working through my CompTIA Linux+ certification, and I say this with reverence: there is deep, quiet dignity in an operating system that is exactly what it promises to be, and absolutely nothing else.

Alpine is the monastery clinging to the side of a frozen mountain. Ascetic to the point of near-invisibility, it uses musl instead of glibc and BusyBox instead of GNU coreutils. The container world reveres Alpine because it boots in milliseconds, occupies five megabytes of disk space, and does precisely what it is told without ever speaking out of turn. It simply exists, minimal and correct, like a hermit who has transcended the need for human language.

Of course, no religion is complete without a vividly imagined Hell, and our world is well supplied with heretics and demons.

The deepest, most fiery pit of Hell is Windows. Windows is Babylon. It is a corrupted, bloated leviathan powered by telemetry, forced updates, and corporate surveillance. To use Windows is to willingly sign over your digital sovereignty to a faceless corporation that views you not as a user, but as a harvestable data crop. Every time Microsoft injects an advertisement into the Start menu, a Linux user gets their wings.

macOS occupies a much more complex theological space: Limbo, or perhaps an exceptionally well-decorated Purgatory. It shares ancient Unix genetic material with the faithful, allowing you to open a terminal and use grep, awk, and sed just like the prophets intended. But the ecosystem is a gilded cage. It is utterly closed, unmodifiable, and strictly controlled by a trillion-dollar corporation with very aggressive opinions about what you are allowed to do with hardware you supposedly own. The people trapped in the Apple ecosystem are capable individuals who have simply chosen aesthetic comfort over freedom.

I say this with the sheepish awareness of someone who actually discovered the command line on a 2018 MacBook Air. That machine was my gateway drug. I found the terminal, realised it was just a zsh emulator, and discovered it could be modified. That tiny distinction–realising the interface was just a mask over the machine–cracked my entire reality open.

My conversion began in earnest last August. Looking at my university degree and the catastrophic state of the Nigerian economy, I concluded that my current trajectory was not going to produce a liveable income. I discovered the concept of DevOps, and subsequently fell headfirst into the Linux rabbit hole. These two events are linked in the same way a first sip of whiskey is linked to waking up in a different state.

I started on that MacBook Air, copying someone’s zshrc configuration from GitHub. I tweaked it, broke it, fixed it, and eventually built a highly customised terminal environment I pretentiously named Aethria Systems. Every time I added a new alias or changed the colour scheme, I versioned it, eventually stopping at version 2.1. It was an objectively absurd amount of emotional and intellectual investment poured into a text configuration file, and I regret absolutely nothing.

My secondary machine was a Lenovo ThinkPad bloated with Windows. I discovered the Windows Subsystem for Linux (WSL2), spent weeks learning the basic incantations of the command line, and eventually grew disgusted by the layer of Microsoft abstraction. I moved to VirtualBox, successfully installed Ubuntu, and decided that was what I would eventually install on bare metal.

Then, a friend intervened. He told me to use Arch.

He delivered the recommendation with the wild-eyed, terrifying conviction of a man who had just returned from the mountaintop with stone tablets. He was relentless. I deleted my Ubuntu ISOs, ordered a blank USB stick, and spent the seven days before its arrival in a state of monastic preparation. I installed, wiped, and reinstalled Arch Linux inside VirtualBox dozens of times, memorising disk partitioning commands and learning to mount file systems. When the stick arrived, I wiped the ThinkPad and installed Arch on bare metal. By November, I had abandoned traditional desktop environments entirely, moving to Hyprland–a dynamic tiling window manager that operates entirely on keyboard shortcuts and requires forty hours of writing C++ configuration files to make it beautiful.

In this religion, the installation is the initiation ritual. Most consumer distributions feature graphical installers that hold your hand, make complex partitioning decisions on your behalf, and deposit you gently into a working desktop. This is pragmatically wonderful and theologically bankrupt. The person who clicks “Next” six times knows they are using Linux; the person who manually formats their EFI partition, compiles their bootloader, and spends a week wrestling with Wayland compositors knows their machine.

These are profoundly different states of knowledge, and the community treats them as such. Outsiders experience this dynamic as toxic gatekeeping; insiders experience it as necessary discernment. You cannot appreciate the cathedral if you did not haul the stones. The Arch Wiki serves as our scripture–vast, exhaustively accurate, and completely unforgiving. It punishes lazy reading and rewards deep meditation. During my initiation, I wrote a comprehensive, step-by-step installation guide based on my own agonising trial and error.

Months later, the very friend who had aggressively evangelised Arch to me decided he was finally ready to install it on his own machine. I went to his house to gloat about my Hyprland workflow, feeling like a twenty-four-year-old wizard manipulating the fabric of the digital universe. I opened his laptop and discovered he was running Manjaro.

Manjaro occupies a highly contested category. It is an Arch-derivative–close enough to the real thing that pure Arch users take its existence as a personal insult. My friend confessed he had attempted to install pure Arch using ChatGPT as his spiritual guide. It had been a bloodbath of hallucinated commands and destroyed partition tables. In a moment of weakness, he downloaded the Manjaro graphical installer and clicked his way to a working desktop.

I offered absolutely no charity. I mocked him with the zeal of a medieval inquisitor.

Later that evening, overcome with guilt, he called me. He was going to wipe the drive and attempt the true path again. He complained the official wiki was too dense, so I sent him my personal guide. An hour later, he called back in despair, staring at a black screen. He had forgotten to install the GRUB bootloader, and informed me that my guide–heavy on rambling philosophical tangents–was actually worse than the wiki. He returned to his AI companion, and they finished the installation together. The deeply unnatural relationship between my friend and his large language model is a matter I refuse to comment on further.

Eventually, I went back to his house and we wiped the machine one last time. I wrote a physical list of checkpoints on a piece of paper. We moved through the ritual manually: Partitioning. Base install. Fstab. Chroot. Bootloader. NetworkManager. Every time we cleared a hurdle, I placed a tick on the paper. He finally achieved a working, pure Arch installation. His soul was saved.

Which brings me back to Lemmy. A few weeks after saving my friend’s soul, I saw a new user asking for a graphical user interface to install packages on Arch. Without a second thought, I typed: If you need a GUI to install packages on Arch, perhaps you should not be using Arch.

My cursor blinked. When exactly did I become this person? When did I mutate into the insufferable gatekeeper standing at the threshold of the temple, demanding purity tests from the peasants?

I hit reply anyway. pacman is the greatest package manager ever coded, and I stand by the architectural substance of the comment. The elitist tone is something I am still unpacking in my quieter moments.

Evangelism is the specific feature of religious communities that generates the maximum amount of friction with the secular world, but it is worth examining why it happens. It is the inescapable consequence of a cosmology that includes a definitive theory of the good life. If you genuinely believe that software freedom matters–that understanding the tools mediating your reality is a moral imperative–then telling your family about Linux is not enthusiasm. It is an act of deep concern. To the outsider, the Linux evangelist is offering incredibly annoying advice about a software preference. To the insider, it is a desperate moral intervention to save a loved one from the Matrix.

And like all faiths, we have an eschatology. We call it the “Year of the Linux Desktop.” It is the most affectionate, enduring joke in the community because it is also the most sincere, desperate hope. Every year, a prophet emerges to announce that the mainstream breakthrough is imminent. Every year, the rapture is delayed. Yet the hope is never fully abandoned. Valve’s Steam Deck has done more to advance desktop adoption in three years than a decade of screaming advocacy. The hardware compatibility nightmare is largely over.

We keep building. We keep writing exhaustive documentation. Another teenager discovers the terminal. Another person wipes Windows and installs Arch. You do not abandon the faith just because the timeline slipped again; you continue because the work itself is the justification.

I have watched communities close themselves off in the name of rigid orthodoxy. I have watched the pastoral function of religion get weaponised into raw political control. I have spent my life rolling my eyes at zealots.

And then I found an operating system. I developed a cosmology, a theory of the good life, and a set of digital values I will absolutely refuse to compromise. I sit in my room writing scripts to automate things that do not need to be automated. I walk friends through ancient initiation rituals, checkbox by checkbox. I post arrogant, gatekeeping comments on decentralised forums and feel a rush of righteous adrenaline when I do.

I have walked this world irreligious, and I have found a religion. Both of these facts are true, and I have finally made my peace with the contradiction.

Use whatever distribution actually serves your needs. But read the wiki. Always read the wiki.