From Arch to Nix: A Descent Into Flakes

The thing is…

Transitioning from Arch to NixOS is more than just an upgrade; at this point, I’d call it a pathology. There’s this indescribable feeling when things start looking "cleaner," more aesthetic, and free of that unnecessary noise that usually clutters a system. That’s exactly why I decided to rebuild my rice from scratch.

When I first installed Arch, I went with a default config I "found"—or maybe it found me. It popped up on my GitHub feed because someone I follow starred it (talk about a convenient Google-reference coincidence), so I dove in. But even though that config saved me time, it was bloated. It completely trashed my motto: "no bloat, just clean proofs." I couldn’t let that slide.

I could have just reinstalled Arch. It’s clean, it’s manual—if you don’t do what I did—but it’s still a mess of side effects. Every pacman -S felt like a scar on the system that you couldn't fully heal without a fight. I got tired of the entropy. I got tired of the OS being a "living entity" where every minor change risked breaking something functional without my permission.

The Shift

So, I decided to say "to hell with it" and entered the rabbit hole of Derivations and Flakes. I didn't do it because it was easy. In fact, after testing everything in a VM, the actual hardware install took me hours—mostly because I’m still a novice in this specific corner of Unix hell. I did it because I wanted total control, immutability, and a reliable rollback system. I wanted my OS to be predictable and efficient. No hidden processes eating up my RAM (which is expensive, btw), and no more "update anxiety" every time I run pacman -Syu.

I’m willing to lose my mind over the Nix learning curve if it means my system won't brick on a whim. NixOS isn't "bad," it’s just a specific kind of hell that I happen to enjoy. When I finally saw my rice running on the metal, I felt that click in my chest. It’s wild to think that just a few declarations in a couple of files define your entire environment. Is it a headache? 100%. If you want a Plug-and-Play (PnP) experience, NixOS is definitely not for you. You’ll have to get your hands dirty in the terminal just to get a friend's dotfiles running.

My Take

Getting used to Nix is going to be a grind, but that’s the fun of it. As a developer, tackling something with a high difficulty ceiling gives the work meaning. Imagine being stuck on Debian—no hate to Debian—coding PHP for 30 years because you were too afraid of a challenge or something that actually adds some excitement to your workflow.

Random Person: "Dylan, isn't NixOS the opposite of 'no-bloat'? You traded Arch’s simplicity for infinite abstraction layers and config files."

Fair point. NixOS eats up disk space because of its rollback system, keeping old versions and isolated dependencies in the /nix/store. But Arch’s "system drift" becomes more of a bloat issue in the long run. After a year, Arch accumulates manual changes you probably didn't document, making it a nightmare to troubleshoot. In NixOS, the "bloat" is on the disk—documented and reproducible—not in your head.

A NixOS user has way more peace of mind. Sure, changing a setting in Arch is "instant," but in Nix, you follow a set of rules to ensure that change is solid. Over time, NixOS wins on stability. If a developer pushes a breaking change to a tool you rely on, Arch might leave you stranded. In NixOS, updates are atomic. They go into the /nix/store and the system only switches via symlinks when it's ready. If it fails? You just boot into a previous generation from GRUB and you’re back to 100% functionality in seconds.

Random Person 2: "Dylan, while you waste days declaring every comma in a .nix file, someone with Linux Mint already finished their project. You traded utility for a configuration fetish."

And they’re right. Setting up NixOS for the first time without experience can take days—it took me two. But that’s a minor cost compared to the collateral damage of a system that isn't easily reproducible.

Think about it: you’re working on a complex project and your PC dies. On NixOS, you just clone your config, run a few commands, and in 15 minutes you have your exact environment back. On a non-reproducible system, you’re stuck trying to remember which obscure packages you had installed six months ago.

I’m not saying NixOS is the Holy Grail. The learning curve is steep, and the /nix/store size can be overwhelming at first. But you can manage that with a few garbage collection rules. In Arch, if you install a package for a one-time task and forget it, it stays there forever. In NixOS, if it’s not in your config, the Garbage Collector wipes it and its dependencies out. It’s built-in hygiene.

Here’s a shot of how my rice is looking right now:

Nothing left to say. Thanks for reading. Big love. ❤️