· Linux  · 4 min read

Why Arch Linux Became My Daily Driver

A simple, lightweight distribution on an open road

A simple, lightweight distribution on an open road

Navigating the Linux landscape often feels like an endless carousel. After spending years with Ubuntu, Ubuntu-based Mint, enterprise-flavored Fedora, and the ever-evolving Tumbleweed, I found myself needing a distribution that simply lets me keep moving forward—no version jumps or surprise reinstalls. Arch Linux delivered exactly that, providing a seamless and lean environment where I control every layer of my system (from kernel to background services) without sacrificing having up-to-date software.

Lessons from the Field

I originally started with Ubuntu years ago when it was new and exciting. But in 2020 the distribution under Canonical took a headstrong approach to their snaps packaging strategy. It also felt like Ubuntu was overly opinionated in what was installed for the user and the non Long Term Support versions felt flaky. This was also around the time that I had enough of Ubuntu’s flavour of Gnome and its constant breaking extensions, lack of built in functionality (which required extensions) and poor hotkey binding which I grew accustomed to in i3 window managers.

My brief journey through Linux Mint highlighted the frustrations of a point-release model: package downloads crawled against a backdrop of limited mirrors and an APT system that felt sluggish compared to Arch’s Pacman experience. Mint’s hardware enablement kernels tried to bridge the gap by jumping from 6.8 to 6.11, but on new AMD hardware, having newer kernels is simply a no brainer for better performance and power efficiency.

Fedora’s promise of the latest kernels and Red Hat backing was tempting, but offset by an upgrade path every 6 months and an opinionated Free Open Source Software (FOSS) attitude. And SELinux still lurked in the background, invading every system operation, occasionally tripping up container workflows and sometimes creating silent problems in applications that were hard to diagnose. I once turned off SELinux completely. When I decided to reenable it, it took a while to rebuild its policies. Fedora feels like an enterprise desktop distribution given its focus on security.

Tumbleweed’s rolling nature initially seemed like the ideal compromise until I encountered SUSE-specific RPM quirks requiring manual repo configurations—an unexpected detour from the “just works” promise of a modern RPM distro. Without the simplicity of Pacman or the breadth of the AUR, I felt like I was managing the distribution more than my development environment.

The Arch Epiphany

Switching to Arch was like trading in a bulky sedan for a nimble sports car. Its pure rolling release philosophy means no more disruptive “version upgrades”—my system simply evolves alongside the upstream community. Pacman, with its binary packages and straightforward commands, made software management a breeze, while the Arch User Repository unlocked near-infinite libraries—from OnlyOffice to obscure command-line utilities—without hunting down external DEBs or RPMs.

By default, Arch stays out of my way: no SELinux or AppArmor enforcing unexpected policies, and minimal services humming in the background unless I explicitly add them. On the graphics front, Wayland on Plasma feels snappier than X11, giving me a tangible performance boost. And when bleeding-edge kernels ever teeter on the brink, the official LTS package stands ready as a safety net—something I sometimes missed on Fedora’s auto-pruning Grub menu.

Embracing the Journey

Of course, Arch isn’t a turnkey solution—it asks for my partnership in maintaining a healthy system. From reading wiki updates before updates to scheduling backups with Timeshift, I’ve taken a more hands-on workflow that keeps me connected to the OS. The community-maintained AUR is a reminder that I’m part of a collaborative ecosystem; if a package languishes, I either pitch in or adapt.

While some enterprise environments shy away from Arch’s custom ethos, I’ve discovered that for developers and power users, the trade-offs are more than worth it. I get the freshest software, a tailored footprint, and the satisfaction of a system that truly reflects my choices.

Final Thoughts

For anyone fed up with the treadmill of point releases and eager to craft their ideal Linux environment, Arch Linux stands out as a shining option. It demands attention, but ultimately delivers a computing experience that feels both personal and perpetually current. Whether you’re on AMD hardware chasing the latest kernel or a developer tired of background policy headaches or upgrade roadmaps, Arch offers a path to a cleaner, faster, and more engaging Linux experience.

Back to Posts

Related Posts

View All Posts »