The MacBook Pro: Apple's Risky Switch to Intel

It’s January 2006, and the Mac world is in shock. For years, we’ve been told that PowerPC was superior to Intel’s "Pentium" architecture. We mocked the "Intel Inside" stickers. But today, Steve Jobs walked onto the stage at Macworld and introduced the MacBook Pro, powered by an Intel Core Duo processor.

Why the Switch?

The reason is simple: "Performance per Watt." The PowerPC G5 was a powerhouse, but it ran so hot that Apple could never fit it into a laptop. They were stuck with the aging G4 while the PC world was racing ahead with dual-core mobile chips.

By switching to Intel, Apple gets access to the most advanced mobile processors in the world.

Rosetta: The Magic Ingredient

The big concern for us developers and users is compatibility. How will our old PowerPC apps run on Intel? The answer is Rosetta—a transparent binary translator that allows PowerPC code to run on Intel Macs.

It’s surprisingly good. While there’s a performance hit, most apps just work. But for high-end software like Photoshop or Final Cut, we’re going to need "Universal Binaries" that contain code for both architectures.

# Developers now have to build for two architectures
gcc -arch i386 -arch ppc myapp.c -o myapp

Boot Camp

The most unexpected side effect of the switch is that these Macs are now, essentially, high-end PCs. You can actually run Windows XP natively on a Mac using Boot Camp. This is a massive selling point for developers who need both OSs.

Looking Ahead

The Intel switch is a huge gamble, but it’s the right move. Apple is no longer tied to the stagnating PowerPC roadmap. The MacBook Pro is sleek, fast, and (mostly) cool. It feels like the beginning of a new golden age for the Mac. Now, if we can just get all our favorite apps recompiled for Intel...