After work, all you really want is some peace and quiet. No debugging, no broken package dependencies. And yet, Arch Linux has been running on my personal machines for years. Even though during the day I deal almost exclusively with Red Hat or Debian.
I'm often asked why I don't just install Windows 11, "when everything just works".
The short answer: Because I categorically reject an opaque black box on my workstation.
Windows 11: I'm No Longer the Admin
Windows hasn't really been a topic for me for over 20 years — I only touch it when it's absolutely unavoidable in a professional context with clients. But when you see what Microsoft is currently doing with Windows 11, I'm grateful for this distance every day. Windows 11 now feels like a huge advertising platform where the actual desktop is just a supporting role.
It starts with small things: The Start menu suddenly forcing web searches via Bing. OneDrive clawing itself into the filesystem uninvited. And now the constant integration of AI features like Copilot that nobody ever asked for. When you set up a machine, you want full control. A Windows user spends the first hour after every fresh install disabling telemetry via registry hacks, turning off Widgets, and taming forced updates.
Nevertheless, you have to be fair: When it comes to obscure proprietary corporate software or simple plug-and-play peripherals, Windows is often the path of least resistance for the general public. It works. The price, however, is a system that strips the user of architectural sovereignty and treats administrative privileges more like non-binding recommendations.
Arch Linux: Freedom Instead of a Golden Cage
So why do I subject myself to Arch? Definitely not because I have too much free time. I use Arch for the absolute freedom and control.
Arch comes naked. You don't get a pre-configured desktop environment where developers decided what you supposedly need. You start with the bootloader and build your system exactly as you need it for your workflow. No bloatware, not a single background service that you didn't consciously start and configure yourself. If something is running, it's because I wanted it that way.
Then there's the rolling release model. There are no major "version upgrades" where you have to pray that half your system doesn't explode around your ears. You install Arch once, and from then on the system rolls along with you. You always have the latest kernel, the newest development tools, and the most modern software. Anyone who, like me, frequently tests new technologies or develops software (like BearWave) doesn't need Ubuntu where system packages are already outdated after a few months.
The Best Package Management in the World
And then, of course, there's pacman and the Arch User Repository (AUR).
Microsoft is trying to catch up with Winget, but that's a toy compared to pacman. Especially in admin daily life on the command line, when I need an obscure infrastructure tool, an old script, or proprietary VPN software — there's a package in the AUR for it. One command, and the thing is downloaded, built, and cleanly integrated into the system. No shady .exe downloads, no annoying installation wizards.
The AUR is both a curse and a blessing: Anyone can upload packages there, so you have to review the build scripts. But together with pacman, it's a weapon that drastically speeds up managing your own workstation.
The Price of Freedom
Of course, this absolute freedom has its price. A rolling release system that always operates on the "bleeding edge" forces you to stay alert.
If you blindly apply updates without ever reading the release notes, it can happen that a Tuesday morning update completely breaks your display manager — exactly five minutes before your first Teams meeting. There's no support, there's only you, the log files, and the Arch Wiki. Honestly? In moments like these, I curse loudly and simply wish for my rock-solid, boring Debian setup from the server.
But: These are my problems that I can fix myself. Not the artificial restrictions of a corporation.
KDE Linux and the Fork Hell
A word about the rest of the Linux world. The extreme fragmentation annoys me. There are hundreds of Ubuntu derivatives (Pop!_OS, Zorin OS, Kubuntu) that all do the same thing at their core but tie up valuable developer resources.
And then there's the trend toward "immutable OS" like the new KDE Linux. A base system that's read-only. Applications are only available via Flatpaks or Snaps. For the average office user, this might be brilliant because they can no longer accidentally break the system. But for me as an admin? An Arch-based system without pacman? Where I'm no longer allowed to install system packages globally? That takes away exactly the freedom that made me switch to Linux in the first place.
Captain in Your Own Engine Room
At the end of the day, you have to decide which price you're willing to pay for your operating system.
Windows 11 costs you system sovereignty, opaque telemetry, and unpredictable interventions. Arch Linux costs you personal responsibility, occasional tinkering sessions, and a steep learning curve.
For me, the decision is clear: I'd rather have a system that occasionally forces me to get my hands dirty in log files than one that overnight turns me into an unpaid beta tester for AI features. Arch Linux isn't perfect, but it's honest. It gives me back exactly the time and knowledge I invest. And above all: It lets me remain the boss on my own hardware.