I didn’t expect a Linux distro to make me curious again. But Omarchy did something unusual — it made me stop treating my system like a black box.
Under the hood, Omarchy is built on Arch Linux. That detail ends up mattering more than I initially expected.
A Bit of Context
I’m coming back to Linux after a bit of a detour. I used Linux Mint as my primary OS for quite a while. It was stable, predictable, and honestly, very comfortable. Eventually, I drifted into macOS / Apple land for a few years — largely because of Apple Silicon.
And to be fair, the hardware is still incredible. Performance per watt, thermals, and battery life — it’s hard not to appreciate what Apple has done there. But the software side didn’t age as well for me.
macOS is polished. It’s cohesive. It works. But compared to Linux, it started to feel limiting. You don’t really get to look under the hood, and even if you try, you’re constantly reminded that it’s not really your system to shape.
So when I decided to come back, it wasn’t because Apple hardware stopped being great. It was because I missed the feeling of Linux.
That decision also pushed me to rethink my setup more broadly. Instead of going back halfway, I built a new machine around it — a Ryzen 9 9950X, 64GB RAM, and an RTX 3070 Ti.
Part of it was curiosity, but mostly it was about ownership. After years on tightly integrated Apple hardware, there’s something refreshing about a machine where every layer feels like a choice.
First Impressions
Omarchy feels different almost immediately. Not flashy or overly polished, and not trying to win you over. It feels intentional.
You can feel its Arch roots in the way it’s put together — minimal assumptions, strong opinions in some places, and openness where it matters. It doesn’t try to hide Linux from you; it nudges you toward it.
At some point, I caught myself thinking — ah, this is Arch (btw) — and everything started to make a bit more sense.
The Kind of Friction I Missed
Coming from Linux Mint (and later macOS), I had gotten used to things just working. That sounds great — until you realize you’ve stopped learning.
Omarchy reintroduces friction, but it’s the right kind. It nudges you to ask what a config is doing, why a service behaves a certain way, and how things are wired together underneath.
With Omarchy, I found myself reading config files instead of avoiding them, checking logs instead of ignoring them, and understanding how different parts of the system connect. It didn’t force me to learn; it simply made learning the natural next step.
One thing that’s made this process much smoother is having AI tools like Claude and Codex close by. When I hit something unfamiliar — a config I don’t fully understand, or a service behaving oddly — I can ask, iterate, and refine in real time.
It doesn’t replace learning, but it compresses the feedback loop. Instead of getting stuck or blindly copying fixes, I can actually understand what’s going on as I go.
From Consumer to Operator
Linux Mint made me a comfortable user. macOS made me an efficient one. Omarchy is nudging me toward becoming an operator.
That distinction matters. A user interacts with tools and expects consistency. An operator understands systems, embraces some complexity, and is comfortable debugging when things break.
This shift is subtle, but meaningful. The system feels closer. There’s less distance between you and what’s happening.
Owning the System Again
One thing I didn’t realize I missed was the feeling of ownership.
With macOS, everything is polished but sealed. With Mint, everything is accessible but abstracted just enough that you don’t need to care. With Omarchy, there’s very little standing between you and the system.
You see the configs, understand the services, and feel the consequences of your changes. It stops being just a tool and starts feeling like something you’re shaping.
Why This Hits Different as a Developer
As developers, we spend most of our time building abstractions — APIs, frameworks, and tooling that hide complexity. Which makes it even more valuable to occasionally go the other way.
Omarchy pulls you closer to the fundamentals: how environments are structured, how systems behave, and how small changes propagate.
It’s not about becoming a Linux expert overnight. It’s about rebuilding the instinct to ask: what’s actually happening here?
Not for Everyone (And That’s the Point)
Omarchy isn’t trying to compete with beginner-friendly distros. It’s not trying to be Linux Mint, and it’s definitely not trying to be macOS.
It still expects a bit more from you — things can break, you might need to debug, and you’re responsible for your system in a way that more polished environments try to shield you from.
And that’s exactly what makes it compelling.
Closing Thoughts
I didn’t switch to Omarchy because I needed a better setup. I switched because I wanted to feel curious again.
Coming from Linux Mint, and after spending a few years in macOS thanks to Apple Silicon, I had gotten used to systems that just worked. Omarchy reminded me that there’s a different kind of satisfaction in understanding why things work.
The hardware I left behind is still excellent. But this software experience feels far more alive.
For the first time in a while, I’m not just using Linux. I’m learning it again — and this time, I’m paying attention.