Why I’m Still Putting Myself Through the Arch Linux Ritual

My laptop screen just flickered back to life with that terrifyingly blank TTY prompt. There’s a specific kind of adrenaline you get from a fresh Arch Linux install. It’s like moving into a new apartment in Ibadan—everything is empty, the walls need painting, and you’re wondering if you should have just stayed where you were. But once you start running those initial commands, it starts feeling like home.

I was looking at a post-installation breakdown recently, and it reminded me of how much we take for granted in our dev environments. Most people just want a browser, but for me, it’s about the piping. Getting the noto-fonts right is the first thing I do. If the typography looks like garbage while I’m staring at code for ten hours, I’m going to have a bad time. I need those CJK and emoji fonts because, let’s be honest, half of my Slack communication is just the "eyes" emoji.

Doing this in a place like Akure, where you’re balancing your power bank charge against the time it takes to download a few gigabytes of Flatpaks, makes you very selective. I saw the guide mentions heavy hitters like Libvirt and Gnome Boxes. I used to be heavy on VMs for testing, but these days I’m leaning more into Podman. It’s lighter. When my laptop fan starts sounding like a generator in an Owerri market, I know I’ve pushed the virtualization too far. Keeping the system lean is a survival skill when you don't want your hardware to throttle in the heat.

The Python section of any setup guide always gets me thinking. Seeing "uv" on the list makes me happy. It’s significantly faster than traditional pip, and when you’re dealing with "Sapa" and every megabyte of data counts, having a tool that handles dependencies efficiently is a lifesaver. I’m moving all my projects over to uv and poetry. No gree for slow builds this year.

Then there’s the editor debate. I’ve been trying to give Zed a real shot lately. It’s built in Rust, it’s snappy, and it doesn't eat RAM like Chrome at a buffet. But I still keep VS Code around because the extensions are just too good to leave behind. It’s like having a favorite spot for Suya—you might try new places, but you know exactly which one hits the spot every time you’re actually hungry.

You can’t talk Arch without the AUR. Whether you’re using yay or paru, it’s the secret sauce. Being able to pull basically any piece of software without hunting for a random .deb file or some broken PPA is why I stick with this distro, despite the occasional "I broke my kernel" headache on a Tuesday morning. It's about that control. I want to know exactly what is running on my machine, from the Bluetooth service to the power profiles.

Setting this all up is a chore, yeah, but it’s my chore. It’s the digital equivalent of sweeping your yard before the sun gets too high in the sky. Once the environment is set, I can finally get back to the actual work of building things.