Why every dev uses a Mac (and why it matters less than it seems)

A subscriber named Goldman asked something that comes back every week in a different form: why do most of the developers he sees use a Mac to code?

The question looks like it's about hardware. It almost never is. It's about status, about the App Store, about the shell and, deep down, about a career decision we avoid admitting: how long it's worth sticking with a machine that's slowing you down.

Fashion and status are real. Denying it is silly

The first honest answer is the one a lot of people avoid writing: fashion is part of it.

A Mac carries status. Showing up to a meeting with a laptop and phone that look sorted conveys a certain consistency. Showing up with equipment that's falling apart also conveys something, just something else. Like it or not, the expensive machine became a visual shortcut for "a professional who takes this seriously". It's the same kind of signal we read without admitting we're reading it.

That doesn't make the Mac a better tool in itself. It makes it a social object. If someone picks it only for that, they're picking a symbol. You can live with that. Just don't confuse a symbol with productivity.

The technical reason that really pinches

In my case, the switch didn't start with looks. It started because a good part of the time I also build mobile apps. With React Native, for example, the targets are Android and iOS. On Windows and Linux you can make progress on Android. On iOS the door closes: native builds, the simulator and publishing to the App Store all go through Apple's ecosystem.

I tried the long way before buying. A machine with lots of RAM, virtualization, trying to run macOS on top. In theory there's memory to spare for the guest. In practice the experience isn't the same. The iOS emulator struggles. Stacking Android inside an emulated Mac inside Windows or Linux becomes a sandwich: it stops working properly and the schedule slips.

When the job is publishing to both stores, the Mac stops being a preference and becomes an operational requirement. You can rent a Mac in the cloud. You can pay for a build service. That solves the final publishing step. It doesn't solve the daily loop of developing, testing and iterating on an app that needs the iOS simulator next to you nearly as well.

That's why I switched. Not because Windows was a sin. Because it was slowing me down on what I needed to deliver.

Unix in your lap, and apps that only exist there

There's a second technical reason that matters even for people who don't touch the App Store: macOS is Unix underneath.

A lot of what we do on servers (scripts, shell, automation) fits with less friction than on classic Windows. People coming from Linux feel less of a break. People coming from Windows feel the jump. It's not magic. It's closeness to the environment where real software usually runs.

And there's the third one: the app ecosystem. At certain times, and still today in several product workflows, interface and design tools only exist properly on the Mac. Sketch is the classic example: it helps you sketch app and website layouts in a way that, for a lot of teams, was the Photoshop/Illustrator of interfaces. When the team's tool is Mac-only, the "which laptop" discussion is over before it starts.

None of these three reasons (App Store, Unix, exclusive apps) is fashion. They're constraints. You respect a constraint or you work around it at a cost. The mistake is mixing up constraint with identity.

A Mac doesn't make you a better developer. It only solves (or doesn't) the friction between what you need to deliver and what your machine lets you do.

You can do almost everything on Windows. I did for years

I spent my whole life on Windows before. Nothing to be ashamed of. You can be very productive there. Most backend, web, studying, freelancing and corporate jobs don't require an apple logo on the lid.

The switch only made sense when the cost of sticking with it got bigger than the cost of changing. That sentence sounds obvious and it's exactly the one we ignore: we keep fighting drivers, VMs, broken builds, "I'll look at it later", while the client's deadline doesn't wait.

In your career, if something is slowing you down professionally and repeatedly, you have to change it. It isn't normal to waste too much time because the machine won't let you. Time lost to environment friction is time that didn't go to the product, the interview, studying, sales.

If Linux or Windows handle your stack, stay. If the problem is the environment, fix the environment. A Mac is one possible answer. It's not the only one. It's the most expensive one in Brazil.

Build quality and price: two details you feel in your hands

There's a physical difference I notice and that I won't romanticize too much: the Mac feels sturdier, more solid. Laptops my employees used, Dell for example, sometimes looked like they'd come apart at the next hinge. The Mac feels like it can keep up. That's finish and product engineering, not a moral argument.

The other detail is money. In Brazil, at the time I recorded this, we were talking about eighteen to twenty thousand reais for a decent Mac. That's an entry-level car decision, not an accessory. Think it through. Run the numbers. If it makes sense, bring one from abroad through someone you trust; that was my way of making it less absurd. Buying for status with money your company or your own pocket doesn't have is the worst reason on the list.

What I'd tell Goldman today

If the question is "why does everyone use one", the short answer is: fashion, status, the App Store, a Unix shell and tools that only run there. In different proportions for each person.

If the useful question is "do I need one", the answer is different: only if your current work is stuck without it, or if the friction of your current machine has already become a measurable cost. Otherwise, stay where you're already productive. Changing laptops doesn't change your seniority.

I still use Windows at times. I use a Mac where it unblocks what I need to publish. The tool follows the work. Not the other way around.

In short

Devs use Macs as a symbol, because Apple's ecosystem requires it, for the closeness to Unix and for apps that have no good equivalent on Windows. All of that can be true at the same time.

What it can't become is a purity test. Windows and Linux are still enough for a huge share of the craft. The right question isn't "which machine makes me look like a dev". It's "which machine stops getting in the way of what I already need to deliver".

When the answer is a Mac, buy it with intent. When it isn't, ignore the feed and go back to the code.

---

Watch the full video at Por que Todo Dev usa Mac? #DevPlenoResponde (in Portuguese). There I answer Goldman's comment with the reasons around fashion, the App Store and Unix, and the criterion for switching machines when one starts slowing down your work.