I have been working in software development for a bit over three years now, and over that time the terminal has become less of a tool for specific tasks and more the environment I default to. This practice is what led me to go through WSL, Ubuntu, and eventually Arch Linux. I could lay out the justifications for my decision at each step, but that is not the focus of this blog. Instead, I will talk about the installation process, how it feels daily driving Arch, and the pros and cons.
Getting Started
As you probably already know, Arch's installation process has a reputation for being difficult, and it is difficult to argue against that for the most part. Full manual partitioning, bootstrapping the base system manually, and configuring the bootloader yourself with no guardrails are not very straightforward. While that method of installation still exists, it is no longer the only option. The official installer, archinstall, has matured into a genuinely capable tool for a guided setup: it walks you through disk configuration, bootloader selection, desktop environment choice, and user setup with a menu-driven interface that is capable of producing a system functionally identical to a manual install, but in a fraction of the time.
It is still worth spending some time with an article or a walkthrough before running it, not necessarily because it is difficult to make sense of, but because it makes your decisions informed. The default options archinstall offers are sensible on their own, so you are unlikely to end up with a broken system even without much prep. However, that research mainly pays off in making choices that fit your specific machine and use case.
Getting Hyprland running took longer than a standard desktop environment would have, mostly because "installing a window manager" on Arch also means configuring your own status bar, notification daemon, application launcher, and lock screen, none of which come bundled.
Hyprland in Practice
Going into Hyprland, I did not have any real technical understanding of what I was configuring. It basically started with .conf files whose exact syntax I could not properly explain, and I was mostly pattern matching off examples: copying keybindings, adjusting values, and slowly building a real intuition for what changed what. This is not really a criticism of the system; if anything, it says something that a fully working, personalized setup was possible without fully understanding the config language on day one.
At some point, the Hyprland developers even moved the whole configuration over to Lua, and adapting to that shift became part of the experience. This did not really feel like a big change though, because the syntax was not the main part of the experience. It was actually the sense that everything is actually mine. Every keybind, animation curve, and rule about how a specific app behaved was something I chose, and that has a much more direct feedback loop than clicking through a bunch of menus and hoping the right toggle exists.
Day-to-day Experience
Adjusting to the workflow itself was actually more straightforward than the initial setup. The Super + number shortcut for switching workspaces was already familiar from previous environments, where it opened the apps in the taskbar in their order. The difference here is that this shortcut opens workspaces instead of specific apps, but there is already a mental map of which number belongs to which app, so the organization is still intact. This looks something like:
Super + 1→ Zen (browser)Super + 2→ Ghostty (terminal)Super + 3→ Obsidian (notes)- and so on for the remaining applications
The only issue with this flow is opening the apps manually in each workspace, which is a trivial matter I just have not fixed yet for some reason. The system has worked consistently well outside of that. Every application has a fixed location, and I know where to find what I need without hunting through overlapping windows.
What Works Well
It Is Extremely Customizable
Nearly every part of the desktop experience is something you define and not inherit. Making the system uniquely yours is just not possible on the most popular OSes, and it is extremely difficult in others.
Package Availability and Freshness
The range of available software, both on the official repositories and the AUR, is extensive. On top of that, updates arrive close to their upstream release instead of being held back for a staged release cycle, so you are guaranteed to get the latest versions of your favorite software.
Hyprland's Performance and Integration
Hyprland is a truly impressive and beautiful piece of software. The tiling window management keeps you organized, and the beautiful animations will make you love your computer even more.
Strong Documentation
The Arch Wiki is the best way to resolve most of the issues you encounter while running Arch. It answers your configuration and troubleshooting questions without needing to search elsewhere, which isn't something you could say confidently about other distributions.
What Doesn't
Aur Security Is an Ongoing Concern
In June 2026, attackers compromised more than 400 AUR packages by taking over previously abandoned ones and modifying their build scripts to install a credential-stealing rootkit capable of concealing itself at the kernel level once granted root access. This was done by impersonating a trusted maintainer and adopting packages with established histories, then introducing malicious code through updates that looked routine. The official Arch repositories were unaffected, as this was specifically an AUR trust-model issue, but it's a direct illustration of a trade-off: the same openness that makes the AUR useful is what makes it a viable attack surface. So you have to be more deliberate about reviewing PKGBUILDs before installing anything from an unfamiliar or recently-transferred package.
Ownership of the Configuration Cuts Both Ways
There's no default to fall back on when something breaks. Every part of the setup is something I built, which means every part of it is also something I'm responsible for fixing.
Conclusion
The switch has been worth it. Not because Arch is objectively superior to Ubuntu, Fedora, or the other distributions, they all actually serve their intended purpose well. The actual value for me is that the setup matches how I actually work instead of requiring me to adapt to it.
That said, this isn't a universal recommendation. If a low-maintenance, mostly invisible operating system that just stays out of your way suits your needs, there's little reason to change that. But for anyone already comfortable in the terminal and inclined to want direct control over how their tools behave, you should really give Arch Linux a shot.