You know the joke. It’s the one developers whisper to each other at conferences, in Slack channels, in the quiet moments between debugging sessions: We build the tools of freedom on machines designed to keep us locked in.
For years, we’ve tolerated the contradiction. We write open-source code on proprietary hardware. We preach decentralization from inside Apple’s walled garden. We champion user autonomy while using a laptop that literally won’t let us install software without a permission slip from Cupertino.
We built the open-source revolution on machines designed to keep us out of our own systems.
And for years, the trade-off made sense. macOS was Unix-based, beautiful, stable. The hardware was unmatched. The friction of staying on Mac was lower than the friction of switching to Linux. So we swallowed the contradictions, paid the Apple Tax, and got back to work.
But something has shifted. The friction equation has flipped.
DHH recently predicted that Linux adoption among programmers is about to go parabolic. Not because Linux suddenly got better — it’s been ready for years. But because Apple is systematically making the Mac worse for the people who actually build things with it.
Look at what’s happening. Notarization requirements tighten with every macOS release. Gatekeeper gets more aggressive. System Integrity Protection locks down directories that used to be yours. The Terminal app hasn’t meaningfully improved in a decade, while Apple focuses on making the Mac more like the iPad — a consumption device, not a creation device.
And then there’s the AI question.
The most important shift in computing in a generation is happening right now, and it’s centered on local AI tooling — running models on your own hardware, with your own data, on your own terms. The open-source AI community is building at breakneck speed. But Apple’s ecosystem constraints make running local AI models increasingly painful. The frameworks lag. The permissions fight you. The hardware is locked behind APIs that prioritize Apple’s vision of AI over yours.
Apple isn’t protecting you. They’re protecting their revenue model from your independence.
This is the part where someone usually jumps in to defend Apple. “But the M-series chips are incredible!” Yes, they are. And that’s exactly what makes this moment so painful. Apple built the best hardware on the market, then wrapped it in an OS that treats developers like children who might hurt themselves if given too much freedom.
The tension has been building for years, but we’re approaching the breaking point. Here’s what the tipping point looks like: The friction of staying on Mac — fighting permissions, working around notarization, accepting Apple’s AI limitations, paying premium prices for a constrained experience — has finally exceeded the friction of switching to Linux.
That’s the shift nobody’s talking about. We keep waiting for Linux to “get good enough” to win over Mac users. We’re asking the wrong question.
Linux didn’t suddenly get good enough. Apple got bad enough.
The migration won’t look like a revolution. It’ll look like a slow bleed that suddenly accelerates. A senior developer here. A startup team there. A solo indie dev who finally got tired of fighting her own operating system. Then the posts start — “I switched to Linux full-time and here’s what happened” — and they don’t say “Linux is perfect.” They say “Linux finally lets me do my job without asking permission.”
That’s the emotional core of this shift. It’s not about features or benchmarks. It’s about the feeling of reclaiming control over your own tools. It’s the moment you realize you’ve been renting your own workstation from a landlord who keeps changing the locks.
Think about the developers you know who’ve already switched. They don’t talk about Linux with the weary pragmatism of someone who made a compromise. They talk about it with the fervor of someone who escaped. There’s a reason for that.
The walled garden has become a prison yard, and the inmates are realizing the door was never locked from the outside.
For Apple, this won’t show up in quarterly earnings for years. The Mac is a fraction of their revenue. They’ll keep optimizing for the average user, the consumer, the person who wants their computer to be an appliance. And that’s fine — most people should have appliances.
But developers aren’t most people. We need to get under the hood. We need to run unconventional software. We need to experiment with AI tools that didn’t come from an App Store. We need an operating system that treats us as the owner, not the tenant.
The parabolic shift DHH is predicting won’t be driven by Linux evangelism. It’ll be driven by developer exhaustion. The exhaustion of paying $2,500 for a laptop that won’t let you install a Python package without jumping through hoops. The exhaustion of watching Apple lock down another system directory. The exhaustion of building the future on a platform that’s increasingly stuck in the past.
If you’re a developer reading this and feeling the friction, here’s the truth nobody at Apple will tell you: The switching cost is real, but it’s finite. It’s a few weeks of discomfort, a few days of configuring your environment, a few moments of missing macOS’s polish. And then it’s over. And you’re free.
The best time to switch to Linux was ten years ago. The second best time is before Apple locks down the next thing you need.
The golden age of macOS for developers wasn’t built by Apple. It was built by the Unix underpinnings that Apple wrapped in chrome and sold back to us. That Unix is still there. It’s called Linux. And it doesn’t ask for your permission.
FAQ
Q: But isn't Linux still too rough around the edges for daily developer use?
A: That was true five years ago. Today, distros like Fedora, Pop!_OS, and Ubuntu deliver polished, stable environments that handle development workflows out of the box. The gap that remains is cosmetic, not functional — and it's shrinking every release while Apple's constraints tighten.
Q: What does this mean for teams standardizing on macOS?
A: Start evaluating cross-platform tooling now. The smartest engineering teams are already building dev environments that don't depend on macOS-specific features. If your entire stack requires a Mac, you're one Apple policy change away from a painful migration.
Q: Isn't this just developer elitism? Most people are fine with macOS.
A: Most people aren't running local AI models, building from source, or fighting permission systems daily. This isn't about the average user — it's about the power users and developers who are hitting Apple's ceiling faster with each macOS release. They're the canaries in the coal mine, and they're already flying out.