The last straw was a software update.
Not a catastrophic one — no data lost, no bricked machine. Just a routine macOS point release that, somewhere in its invisible machinery, decided my preferred terminal emulator should open 40% slower and that a Python environment I'd spent an afternoon configuring should quietly stop recognizing its own path variables. I sat there, coffee going cold, running echo $PATH for the fourth time like it might eventually say something different. It didn't. I'd been on Apple hardware for a little over ten years at that point, and I remember thinking: I don't actually understand this machine anymore. I'm not sure I'm allowed to.
That feeling — of being a polite guest in your own computer — is what eventually pushed me toward Linux. Not the price, not ideology, not a Reddit thread. Just a slow accumulation of moments where the abstraction Apple had so elegantly constructed started to feel less like a gift and more like a wall.
The Decade That Built the Habit
I came to the MacBook the way a lot of writers and developers did in the early 2010s: it was the machine that didn't make you choose. You got Unix underneath and a beautiful surface on top. The terminal was real. The fonts were gorgeous. You could run your dev tools and open Keynote in the same afternoon without feeling like you were living a double life.
For years, that bargain held. I wrote probably two million words on MacBooks — essays, documentation, half a novel that will never see daylight. I shipped code on them. I interviewed people for podcasts on them. The hardware was, for a long stretch, genuinely the best in the business: the keyboards before the butterfly disaster, the trackpads that still feel like a benchmark, the way the whole thing just worked in a way that let you forget you were using a computer at all.
But somewhere around 2019, I started noticing the seams.
The butterfly keyboard era had already shaken my confidence in Apple's willingness to prioritize engineering over aesthetics. Then came the T2 chip, which introduced a layer of security so aggressive it occasionally locked me out of my own boot process. Then the M1 transition — genuinely impressive silicon, but paired with an ARM architecture that meant my existing toolkit needed months of patches and workarounds before it felt stable again. Each of these was, individually, survivable. Together, they told a story about a company whose interests and mine were slowly diverging.
What Linux Actually Costs You
I want to be honest here, because the switch-to-Linux narrative online has a tendency toward triumphalism that I find slightly dishonest. There are real costs.
The first month was humbling. I bought a ThinkPad X1 Carbon — a machine with excellent Linux support, as these things go — installed Fedora, and immediately spent three evenings getting suspend-to-RAM to behave correctly. Not because Fedora is bad. Because hardware compatibility on Linux is a negotiation, not a guarantee, and I'd picked a relatively easy machine. Someone on a more exotic laptop would have had a harder time.
I also lost some software I'd grown genuinely fond of. Craft, the notes app I'd been using for two years, is macOS-only. So is the version of Logic I'd used for podcast editing. I found replacements — Obsidian for notes, Ardour for audio — but replacements are not the same as continuations. There's a switching cost measured not in dollars but in the muscle memory you built up over years, the workflows that lived in your fingers before they lived in your head.
And iMessage. Let's not pretend iMessage isn't a genuine lock-in mechanism. I moved to Signal for most conversations and accepted that some group chats would simply become inaccessible to me. That's a social cost, not just a technical one.
So why did I stay?
The Thing Nobody Tells You About Owning Your Machine
About six weeks in, something shifted. I was configuring my window manager — I'd landed on GNOME but was experimenting with tiling — and I realized I had spent two hours doing something that would have been impossible on macOS without third-party hacks, and I wasn't frustrated. I was interested. The machine was responding to me. I asked it to do something unusual and it did it, without requiring me to wait for Apple to decide that was a feature worth shipping in 2026.
That sounds small. It isn't.
When you use a MacBook for long enough, you start to internalize Apple's opinions about how you should work. One window per screen. The dock at the bottom. Spaces managed a particular way. These aren't bad opinions — they're the product of serious design thought — but they are opinions, and after a decade, I'd mistaken them for facts. Linux, even in its most polished distributions, hands the opinions back to you. You can ignore them, keep them, or replace them entirely. The blank-canvas feeling is disorienting at first and then, gradually, clarifying.
I also started to understand my own tools again. On macOS, I'd grown accustomed to things working without knowing why. On Linux, I had to know why — and that knowledge turned out to be useful. I'm a better troubleshooter now. I understand more about how networking, file systems, and process management actually work, not because Linux is harder (though sometimes it is) but because this guide to fail2ban configuration and similar resources taught me that Linux doesn't hide the machinery as aggressively. The abstraction is thinner, and thinness here is a feature.
A Year Later, Sitting With the Tradeoffs
I've been on Linux full-time for about fourteen months now. The ThinkPad runs Fedora 40. My terminal emulator opens instantly. My Python environments stay where I put them.
I still miss the MacBook trackpad — nothing on the PC side matches it, and I've tried three different external options. I still occasionally hit a piece of software that assumes I'm on macOS or Windows and offers me nothing. I still explain to people, more often than I'd like, why I can't just join the iMessage thread.
But I've also stopped feeling like a guest. That's the phrase I keep coming back to when people ask me why I switched from MacBook to Linux, and I think it's the most accurate one I have. Apple's ecosystem is a beautiful hotel: the beds are excellent, the service is impeccable, and you are absolutely not allowed to knock down a wall.
Linux is more like a house you're still finishing. The bones are good. Some of the rooms are drafty. But you can knock down the wall.
What I didn't expect — what nobody in the breathless switch-to-Linux Reddit posts warned me about — was how much of my frustration with the MacBook had been invisible to me while I was living inside it. You don't notice the weight of someone else's opinions until you put them down. I thought I was switching operating systems. It turned out I was switching relationships: from one where the other party was quietly making decisions on my behalf, to one where I was expected to make them myself.
I'm not sure that's better for everyone. I'm fairly sure it's better for me.
The question worth sitting with, if you're at the edge of a similar decision, isn't which operating system has better specs or a cleaner interface. It's a more personal one: do you want a machine that thinks for you, or one that waits to find out what you think?