The London Underground. The London Underground.

London, UK
June 25, 2006
Apple | Cool | Disney | Entertainment | Fitness | Geek | Microsoft | Politics | Seattle Storm | Transit | Travel | UW MBA

« Meet And Greet | Main | Another Childhood Memory Bites The Dust »

January 22, 2006

Prediction: XP Is The "New Classic" Under 10.5

Since the unveiling of the Intel Macs, the Mac blogosphere has been all atwitter about the possibility that the new iMac and MacBookPro (it's two weeks later, and I still hate that name) will run Windows.

Most of the conversations are focusing on the technical details of such a move, looking at whether or not Windows supports Apple's new EFI BIOS (XP does not, but Vista will), and how hacks might conceivably allow one to get around any technical challenges. But the envisioned scenario - installing some kind of shim to dual-boot between Windows and OS X - requires a fabulous level of geek knowledge in order to work. While the Alpha Nerds among us will certainly make this happen (just as they've managed to poke and prod OS X for Intel so it runs on, say, a Dell), Ma and Pa Mac User will certainly never go to these lengths in their day-to-day lives.

Most of these conversations, I think, are missing the point. There is absolutely no doubt that the new Macs will run Windows. In fact, I predict that Apple is working on a system to make this happen, and it will ship with the next iteration of Mac OS X - 10.5, or "Leopard".

(Quick disclaimer: Yes, I work for Microsoft. But, no, I don't know anything about any of this from my job. This is just a best guess, based on my having watched the Mac market for a long, long time.)

Apple's decision to select Intel processors for its machines has three big benefits. Of these, Apple has only talked about one of them. They are:

Benefit #1: Performance Per Watt. Yes, Steve got up at WWDC in June and waxed rhapsodic about Intel's "performance per watt" - for each X of juice the chip takes in, it pumps out Y amount of performance. The thinking here is that the Intel iron allows Apple to provide G5-class performance with substantially less energy (and, thus, heat) than the G5 itself. Theoretically, this will allow Macs to be smaller, offer better battery life, and sport more innovative designs (big, chunky heat sinks tend to be a design constraint, you know?).

I expect some new, kick-ass designs from Apple later this year.

Benefit #2: Reduced Point Of Difference With The PC World. A secondary, but little-discussed benefit of going to Intel is that Apple no longer has to shoulder the burden of proof that the PowerPC is a good processor. Apple has spent hundreds of millions of marketing dollars working to convince people that the PowerPC chip gave Macs a performance edge. This was, ultimately, a losing battle. Consumers only have so much attention to give any one company, so every precious moment Apple used to defend the PowerPC was one less moment it had to talk about what makes the Mac experience better. By and large, people don't care about processors - they care about buying something that works as advertised. And for a lot of people, something that's too different - namely, a different processor plus a different operating system - feels risky, which then makes them averse to buying your stuff. Most people feel safe in numbers, so they tend to go with what "the crowd" goes with (e.g., Dell). It's the "When Harry Met Sally" principle of computer buying: "I'll have what she's having."

Apple no longer has to fight this fight. Instead, its message can be 100% focused on what makes the Mac a better computer. The debate is now about features, benefits, and ease-of-use. I think Apple is well-suited to fight that battle.

Benefit #3: Binary Compatibility With Windows. This third point is at the heart of this post. By going to Intel (as opposed to the Sparc, or the Cell, or any one of a billion other chip designs Apple could have selected), Apple now has binary compatibility with Windows, and, by extension, the entire family of Windows applications that exist in the world. This is the centerpiece of Apple's strategy for the next 5 years. Leopard's going to exploit this benefit like nobody's business.

Look, it's been possible to run Windows on the Mac for at least the last decade. Programs like Virtual PC have allowed you to install and run Windows as a Macintosh application. The big drawbacks of the Virtual PC approach were performance and experience. Performance-wise, since Windows is compiled for the Intel processor, Virtual PC had to translate the Intel instruction into a PowerPC instruction (much as Apple's Rosetta technology does, but in the reverse direction). This translation process takes time, and makes applications feel sluggish. And on the experience side, all your Windows programs run inside your single Virtual PC window, which means you have to drag-and-drop your files and whatnot between your "real" Mac and your "virtual" Windows machine. This is not optimal for lots of reasons, but the Virtual PC team did an amazing job of making it as seamless as possible.

Today, all that's out the window.

With binary compatibility, we don't need to worry about emulation any more - it's Intel all the way down. Thus, a Windows application running on an Intel Mac will be as fast as it would be running on the same-speed machine from Dell.

And on the experience side, well, I suspect that Apple is working to make that pretty seamless. And the only way they can do that is to build compatibility for Windows software right in to the operating system directly. As it happens, Apple has a lot of experience doing this - namely, with Classic and with X Windows. In both cases, Apple made it possible for programs written for other operating systems and environments to work natively, and seamlessly, on Mac OS X.

"But why?" you ask. "Why would Apple want to embed Windows compatibility into Leopard? Isn't that just sleeping with the enemy and helping Microsoft?"

First, as far as "sleeping with the enemy," let's be clear. Apple and Microsoft have a deep and complex relationship. Microsoft develops some great software for the Mac, and Apple cross-licenses patents with Microsoft. Steve Jobs and Bill Gates have known each other for decades, and built this industry together. Yes, Apple and Microsoft compete in a lot of areas, such as operating systems, digital music, and video standards, but the technology business is one where everything's in a shade of gray, rather than black-and-white. So if Steve's strategy to grow the Mac business makes Bill a few million in new Windows licenses, well, Steve'll do it. No question.

But as to "why?" - Apple wants to build binary compatibility into the operating system because it's necessary. Getting consumers to switch to a Mac is much, much harder than anyone at Apple originally thought it would be. The "Switch" campaign of a few years ago is regarded as a failure not because the message was wrong, or the ideas were bad - "Switch" failed because nobody at Apple really understood what they were asking consumers to do.

Your PC is a crazy thing, a thicket of programs and data files that you rely on to get your work done. And, generally, every program that exits for Windows exists for the Macintosh. But while "generally" existing is good enough to keep the platform viable, it's not enough to get people to jump ship. People get used to one specific thing, and the "general" replacement just doesn't cut it.

Here's an example. Let's say your grandmother is sick of spyware and all the cruft of her PC. So you say, "Hey, Grandma, let's get you a Mac." She does e-mail, of course, writes the occasional letter, balances her checkbook and browses the Web - should be no problem. The Mac does all that stuff.

But as you get in to talking with her, you then find out that she also uses her computer to play solitaire, and has developed a real love of Sudoku puzzles. And furthermore, she loves the programs she's using to play these games on her PC today. Suddenly, your "simple" migration to the Mac is now a hairy pain in the ass - your grandma doesn't want the Mac if she has to give up her favorite solitaire game. And so, after much hemming and hawing and thinking about it, you buy her a new HP laptop and double up on your antivirus subscription. No switch for you.

Trust me: this scenario has played out millions of times over the past few years. There's always that one damn application that the potential switcher loves, or cannot live without. And that's what's been killing Apple's potential for growing the Mac base in any significant numbers.

By including Windows compatibility in Leopard - making it, in effect, the "new Classic" - Apple can now sell a machine to your grandmother. She'll use Safari for the Web, Mail.app for her e-mail, and will run Windows (as a process) for her Solitaire game ... until she finds a new, better Solitaire game for the Mac, and then kicks the old Windows one to the curb. (And, I should point out, that Windows on a state-of-the-art Mac will feel smokin' next to a couple-year-old PC.)

Apple's gonna migrate Windows users to Mac OS X the exact same way they migrated Mac OS 9 users to Mac OS X: through embrace and extend. Take the old OS, run it as a process, make it seamless. Then sell users on the beauty and power of native Mac applications.

Legally, I predict that Apple will get Windows on the Mac the same way Connectix did with Virtual PC - they'll just license Windows from Microsoft. This has the advantage of providing a higher-quality Windows experience, and also ensures that Microsoft is making more money (and, hey, we like to make money) on the Mac.

In terms of migration, Apple will probably offer something like their migration assistant to make it dead-bang-easy for people to move their files from a PC to the Mac. I envision some kind of bootable CD that turns your old PC into a big USB Mass Storage device. From there, you'll simply run a USB 2.0 cable between your Mac and PC; the Mac'll suck over the entire drive, creating a disk image in the process. The disk image will be a freeze-dried copy of your PC data, files, and whatnot; this prevents any kind of nasty commingling of files in the Mac OS X file system, and also prevents disk formatting problems.

If Apple's really sharp, they'll take this migration one step farther, ala Move2Mac, and import your IE favorites, convert your Outlook Express mail to Mail.app, and even set up users on your Mac that are similar to those on your PC. (They might even be able to move your Windows license, too, which could save you some money.)

So yes, Virginia, you'll be able to run Windows on the Mac. And soon, I'd wager - Leopard is due in "early 2007" (which sounds like a MacWorld keynote to me). And from there, I predict that Apple will see their market share double in about two years. The barriers to switching will be, for all intents and purposes, gone.

Interestingly, the new Intel macs are the first Mac OS X machines not to run Classic. In its place, Apple is going to introduce the "new Classic" - Windows XP. It's funny how things work out.

Posted by Gavin Shearer at January 22, 2006 4:52 PM. Posted to Apple.

Comments

Sorry to pick a nit, but I'm not sure I understand what "binary compatibility with Windows" means.

A binary compiled for OS X for Intel will clearly not run on Windows XP, so calling it "binary compatibility" can be misleading. Rather, your third benefit might better be called "Native Emulation".

Finally, you omit the fourth benefit, which is tied to the benefits of Native Emulation Apple can blow the dust off the "Yellow Box for Intel" product and release a Windows XP/Vista compatibility library to allow OS X programs to run on Windows. You might argue this might be a disincentive to buy a Mac, but it could become part of a key strategy for Apple to expand beyond single digit marketshare.

Ultimately, I agree that since both Windows and MacOS X will be running on the same processor architecture, many new compatibility environments that previously would have been shelved due to performance penalties will be back on the front burner.

One final point-- one of the most effective ways to pull of multi-OS implementations on Intel architectures is VMWare. If Apple advocates, buys or licenses this technology, they wouldn't even need to build anything remotely like Classic into OS X.

Posted by: Khan Klatt at January 22, 2006 11:25 PM

A couple of concerns. First, completely licensing windows -- shudder -- would open up the mac to the spyware/virus/clunkiness that consumers are ostensibly fleeing in switching in the first place. So, aside from the inherent ideological problems of Apple shelling out for oem licenses, I have trouble imagining this without a ton of work to create a sort of windows lite implementation. And what kind of resources and access to the MS codebase would that require? Reverse engineering Windows APIs, or simply adopting wine or vmware seems much easier.

The other thing I worry about is the incentive effects on mac software development. It has taken a long time for cocoa to catch on, especially for products offered on both platforms. Will there be an incentive to offer OS X versions when Windows apps run on the mac? Clearly, it won't work as well as a native OS X app, but even if natively emulated apps run well under the hood, it will still be a computing frankenstein. How does that achieve Apple's long term goals?

Anyway Gavin, intriguing idea. I do still feel like there is something more to the shift than performance and energy consumption, as important as that is. Although given some the conflicting statements out of IBM, maybe it was as simple as the failure to provide a laptop suitable G5 (which still defies comprehension).

Posted by: Chris at January 23, 2006 8:49 AM

apple's new efi bios ... you mean, intel's efi ...

benefit 1 - it will mean more power with roughly same battery life
benefit 2 - you haven't seen apple's new ad about intel's cpu inside mac?
benefit 3 - me too has no clue as to what "binary compatibility" means ... softs talk to OS, OS talks to cpu ...

and guess you haven't seen "migration assistant" in yr apps folder ...

Posted by: gr33n at January 24, 2006 3:58 AM

A good read.

Posted by: coelomic at April 7, 2006 12:57 PM

Khan Klatt said:

> one of the most effective ways to pull of [sic]
> multi-OS implementations on Intel architectures is
> VMWare. If Apple advocates, buys or licenses this
> technology, they wouldn't even need to build
> anything remotely like Classic into OS X.

But Classic is not the same as VMWare - Classic is *better* than VMWare. Classic, apps are not constrained to a window. The Classic OS runs in an invisible layer, and Classic applications intermingle with Mac OS X native applications. integration is tighter. Copy and paste between the two largely just works, etc. VMWare doesn't give you nearly the same integration that I think Apple would be looking for.

Posted by: Anonymous at April 7, 2006 1:07 PM

Wow, you posted this back in January? Holy shit, dude. Why aren't you making the big bucks writing for magazines instead of assholes like Dvorak?

Posted by: The Valrus at April 8, 2006 7:28 AM

Nice summary. I agree with you almost all the way, although I'm not sure Apple will go so far as to bundle Windows even for switchers... maybe they will, but it seems like Jobs' ego might stand in the way. If I were a betting man, I'd bet that they will force people to buy Windows out-of-pocket. For Apple, this has the added benefit of making people angry at Microsoft about how much Windows costs as an a la carte item when they get OSX for "free". :-)

Also, FWIW, you can't direct-connect two computers with USB 2.0 like you can with FireWire.

FireWire is peer-to-peer. That means that all devices are equal on the bus but can establish protocol relationships. (For example, a HD can be an SBP2 provider and a computer an SBP2 client.) That's why you can have a computer act like a HD via target disk mode; it just stops acting like a host and starts acting like a hard drive. It's also why FireWire cables are the same on both ends.

USB is host-device. There is a bus master which is the main computer, and everything else is a slave. You can't hook two computers together directly via a normal USB connection because it violates the entire spec from top to bottom. A host cannot act as a device, and vice versa. That's also why USB cables are directional, and have a host side and a device side.

If they do a copy-all-my-files thing it'll have to be via the local network, since that's the only working peer-to-peer port that a standard PC and a Mac share.

Posted by: Drew Thaler at April 12, 2006 8:37 AM

Or it may be that Apple will force people to buy Windows a la carte for a little while even after Leopard ships -- maybe for six months or less, just long enough to get the early adopters tweaked at the price. Then, magnanimously, Jobs will announce that Apple has signed a special deal with Microsoft to distribute Windows for less when you buy it direct from Apple.

The deal won't be that unusual, of course, probably just a variant of a pretty typical OEM deal. But the announcement will paint Steve as the hero who's saving money for all of Apple's customers, and conveniently make the price reasonable just at the time when the sales start moving beyond early adopters.

Microsoft probably wouldn't even mind. Heck, they'd probably be happy if Apple forced people to buy retail copies for a while. I doubt OEM+retail sales of Windows are really where Microsoft's profit comes from...

Posted by: Drew Thaler at April 12, 2006 8:58 AM

What I think will happen is Apple will eiter stick with Bootcamp and just allow people to dual boot. Microsoft could do VPC 8 that could work in the same way as Classic. Or they could go all the way and do the above mentioned "new classic". What Apple should do though is make sure there is a "new classic" for the PPC macs. Perhaps a reverse rosetta could give enough power to run windows apps rather than the rubbish 290mhz I get in VPC 7.

A small question: is translating code (eg: rosetta) faster than emulating (eg: VPC)?

Posted by: Christopher at April 30, 2006 2:35 PM

Post a comment

Thanks for signing in, . Now you can comment. (sign out)

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)


Remember me?


« Meet And Greet | Main | Another Childhood Memory Bites The Dust »