My Mac Is Useless for Local AI. My Windows Laptop Isn't.

I own two laptops. A 2020 Intel MacBook Air, 8GB RAM, no unified memory, gifted by my sister. And a Windows machine: Intel i5 11th Gen, integrated graphics, 16GB RAM.

A tweet made the rounds recently arguing that local AI makes no financial sense. Add up the hardware, the power bill, the hours spent fiddling with quantization settings, and you get a number. Compare that number to years of a frontier lab subscription. The subscription wins, easily. The tweet lists three reasons anyone still bothers running models locally: it's fun, it's cool, or you hate the labs.

I build offline tools for a living, from Port Harcourt. None of those three are the real reason. My own two laptops make the actual case better than the math does.

The Mac can't do this. The Dell already did.

The Mac is close to useless for local model work. No Apple Silicon means no unified memory advantage. No fan means it throttles under sustained load. 8GB doesn't fit anything past a tiny quantized model. It's a fine machine for writing and light coding. It is not a machine you run inference on.

The Windows laptop is the one that's actually done real work. I built StacksNG, an offline AI coding assistant for the African developer stack (Paystack, Flutterwave, Monnify, Termii), entirely on that Dell, for the Africa Deep Tech Challenge 2026. No discrete GPU. Just Ollama, a 7B coding model, and a RAG pipeline running on integrated graphics. It works because I built it for the hardware constraints instead of around them.

That's the split nobody in the "just pay for the subscription" argument accounts for. The machine you already have decides a lot of what local AI costs you. Sometimes it's free, because you own hardware that can already do it. Sometimes it's a wall.

Why I'm renting a GPU before I buy anything

I'm looking at upgrading the Mac, likely to an M4 Pro or a Mac mini M4 with 24GB or more of unified memory, enough to run a 27B-class model comfortably. I'm not buying yet. I'm renting GPU time first.

I don't know exactly what I need until I've actually run something heavier. An RTX 4090 instance on RunPod or Vast.ai runs $0.35-0.55/hr. A few hours of testing costs less than a plate of jollof rice and tells me more about real RAM and throughput needs than any spec sheet. Whatever hardware I buy will be based on that data, not a guess.

Power in Port Harcourt is not something you build a plan around and forget. A local setup that assumes 24/7 uptime is a bet on infrastructure that doesn't always hold. And that's before you get to the part I wrote about separately: an API call from here is a physical trip across submarine cable to a data center that isn't yours, and the same prompt can come back instant one day and sluggish the next depending on load you can't see from Port Harcourt. Renting for the experimentation phase means I'm not sinking money into hardware before I know it's the right call.

If money were no object, an M5 Mac Studio Ultra would fix basically everything in this post. I could kill for one. But it's a wish list, not a plan. Renting is what you do while it stays one.

The honest middle ground

Cloud models aren't wrong. Frontier intelligence at scale is genuinely hard to replicate locally. Keep frontier models for tasks that actually need frontier reasoning. Push high-volume, low-stakes, or offline-required work to whatever you can run locally, on hardware you already have or hardware you've actually tested against your real workload.

The question was never local or cloud. It's which tasks actually need the thing you're paying a premium for, and which ones don't. For a lot of the world building software, that answer depends on things a hardware price comparison never touches: what infrastructure you can actually count on, and what happens to your work when the connection or the power doesn't.