The Distro Hopping Arc: From Windows to Arch Linux
The Distro Hopping Arc
Every Linux user has a story. It usually starts with frustration, moves through confusion, passes through a phase of "I broke my bootloader," and ends, hopefully, with a system that feels like an extension of oneself.
My journey wasn't a straight line; it was a series of experiments, failures, and realizations that led me from the restrictive safety of Windows to the absolute freedom of Arch Linux.
Phase 1: The Windows Era (10 & 11)
Like most people, I started on Windows 10. It was familiar, supported everything, and "just worked", until it didn't. The forced updates, the telemetry, and the bloat started to wear on me.
Then came Windows 11. The centered taskbar and rounded corners looked nice, but underneath, it felt even more locked down. Customizing the UI required shady third-party tools that broke with every update. As a developer, fighting your OS to set up a simple environment feels wrong. I needed a way out.
Phase 2: The Gateway Drug (Ubuntu)
I dipped my toes in with Ubuntu. It was the safe choice, the "standard" Linux.
For the first time, I had a terminal that felt powerful. apt install was a revelation compared to hunting for .exe installers. But after a few months, the cracks appeared. Snap packages were slow, and GNOME, while polished, felt rigid. I wanted to change how my window manager worked, but Ubuntu fought back. It was Linux, but it was their Linux, not mine.
Phase 3: The Declarative Dream (NixOS)
I decided to jump into the deep end with NixOS. The promise was intoxicating: a completely reproducible system defined in a single configuration file. If I broke something, I could just rollback.
The reality? It was brilliant, but isolating. Need to run a simple binary you downloaded? Write a shell derivation. Want to change a config file? You can't edit it directly; you have to rebuild the system. While I loved the philosophy, the friction for day-to-day tasks was too high. I spent more time packaging software than using it.
Phase 4: The Endgame (Arch Linux)
Finally, I landed on Arch Linux.
People meme about "I use Arch, btw," but there is a reason it sticks. Arch gave me a blank canvas. It didn't assume I wanted a desktop environment, a specific audio server, or a browser. It gave me a package manager (pacman) and the AUR (Arch User Repository).
The AUR is the killer feature. If software exists for Linux, it is in the AUR. No PPAs, no hunting for RPMs.
Why I Stayed
Combined with Hyprland, Arch became the ultimate creative tool.
- Simplicity: My system only runs what I tell it to.
- Rolling Release: I always have the latest tools (Neovim, compilers, drivers).
- Control: If a config file changes, it's because I changed it.
The journey from Windows to Arch wasn't just about changing software; it was about changing my mindset. I stopped being a "user" of an operating system and became its "administrator."
And yes, I broke my system a few times along the way. But fixing it taught me more about computers than years of using Windows ever did.