But, QuarkXPress 7 already runs on Intel-Macs, say some. That is not entirely true. QuarkXPress 7 is still in beta, albeit a public beta. Despite the close relationship between Apple and Quark, Quark is not calling their Intel-Mac-compatible application ready for release. Whether it is or is not ready is irrelevant; Quark is cautiously allowing a shakedown period for the Intel-Mac and Quark’s flagship application running on that platform. Wisely, Quark is taking advantage of the visibility and goodwill earned by being the first major application publicly announcing compatibility, but also, even more wisely, is not fully committing to the untried Intel-Mac systems by releasing a dot-oh shipping product. Whether QuarkXPress 7.0 succeeds or fails is a critical matter for Quark; it may very well decide whether XPress continues to be a major market player, or is relegated to the abyss of “legacy software.†While maintaining good relations with Apple and Mac customers is crucial to the survival of Quark’s software business, delivering a product that works is the highest priority. Releasing XPress 7 for Intel-Macs too early puts the application–and the company–at risk for bugs in the Intel-Mac hardware or operating system to cause showstopper failures in XPress–which would be a market share and public relations disaster for Quark even if the issues were beyond Quark’s control.
Adobe, Microsoft, and other large developers of Mac software face the same concerns as Quark. Software developers are leery of Apple’s history of rushing products to market without thorough testing. Mac fans will recall the not-quite-ready-for-primetime Macintosh OS X 10.0, and the fact that Apple did not afford software developers sufficient lead-time to work with the final OS X 10.0 development build and SDK before the operating system was released to the public.
“Why wait for Creative Suite 3,†someone recently asked me. “Adobe should just [port] CS2 versions of [their applications] today.†Why? What is the benefit to Adobe customers of purchasing–even if only for the cost of media and shipping–another copy of Creative Suite 2 or CS2-version applications simply for installation on an Intel-Mac? “Because customers want to use Intel-Macs,†is the usual reply. Setting aside bragging rights and the coolness factor of being an early Intel-Mac adopter, logically considered, there is no significant benefit to obtaining and installing a recompiled version of Creative Suite 2. Certainly not one that justifies the added expense of purchasing–again, even if only for the cost of media and delivery–as well as the necessity to activate the software and reconfigure its preferences and workspaces.
Additionally, even an Intel-Mac-compatible version of Creative Suite 2 does not satisfy every creative pro’s application needs. How will those PDF proofs be sent to clients if Entourage, Thunderbird, and other email applications haven’t yet been ported? Sure, iMail works on Intel-Macs, but does iMail satisfy everyone’s needs? How will one preflight and impose those PDFs? InCopy is only slowly penetrating the market; how will the average user write word processor files for placement into InDesign? Where does a Creative Suite-based workflow break down when workflow-critical plug-ins will not run? Font Book is a good introductory font manager, but with what will professionals manage fonts used by the Creative Suite? How reliable is the color input to, and output from, Photoshop if spectrophotometer and device color calibration software isn’t yet available for the new processor chip? What about printing and scanning? Early versions of OS X had serious issues with the drivers from major printer manufacturers (many Hewlett-Packard printer owners had to jump back to Classic Mode just to print!); what are the chances that Apple and all the hardware manufacturers have ironed out all the compatibility issues this time around?
Rarely does an entire creative workflow run solely on Adobe’s creative pro applications. Even if Adobe released its products for Intel-Mac today, workflows would break down the moment they required an application, plug-in, or technology that hadn’t yet been recompiled for Mac-Intel. Initially, stubborn Intel-Mac users would find themselves juggling projects and assets between two machines; ultimately, they would choose productivity over coolness by switching back to the older Power Mac that does run everything needed to get the job done.
Adobe will port its applications to Intel-Macs–probably with Creative Suite 3–which I predict won’t be released until January of 2007, if not as late as April. In turn, Microsoft and all the other Mac software and hardware developers, large and small, will also port their products to Rosetta. But, they will do it in time, after the Intel-Mac platform has proven itself, and after the respective software makers have verified to their own satisfaction that their products are ready to be released for that platform. It is in the best interests of these companies to get Intel-Mac-compatible versions of their products to market as soon as possible, but not at the expense of reliability, functionality, performance, or customer satisfaction.
In the meantime, have patience. Intel-Macs may be faster and more powerful, but faster and more powerful doing what?
Many of these arguments are valid, but miss the broader point. Apple and Adobe have done a poor job of allowing professional users to anticipate a roadmap for the future. If I’m forced to purchase a new Mac based system today, what do I buy? A PPC based G5 that will be obselete in the near future and offer sub par performance once the universal apps hit the shelves. An Intel based Mac and live with Rosetta enulation slowing everything down, then face a unclear upgrade future that probably involves purchasing software a second time? Or do I just dump Apple and go to Windows where the roadmap is clear and application performance is better? I find it funny that Apple named their emulation layer for a artifact that finally gave us insight to the past, while their approach to professional users continues to show thay have learned nothing from their history.
Windows has a clear roadmap??!!!!
Shirley, you jest.
The past has shown us that there is no way to predict a clear roadmap for the future.
All sorts of puns about roads come to mind, but I will (with diffuculty) restrain myself.
Brian, Jim gets straight to the point: There are no roadmaps to be had. Apple and especially Adobe are responsible for most of the little predictability we have in professional creative and production technologies. Apple brought the graphical user interface to market, priced laser printers within reach of individuals, and created the concept of Plug N’ Play, among many other innovations. Adobe created the printer language on which Apple’s laser printer ran, pioneered non-device resident soft fonts, developed PDF, and is the innovator behind an overwhelming majority of the applications, systems, and methodologies we use to do our jobs. Because of them we know today’s PDFs will work in tomorrow’s workflows, our fonts will serve us for many years to come, and that today’s Macs can exchange files with tomorrow’s PCs (and vice versa).
With the breakneck pace of technology development, there isn’t very much more one can plan on. I think both companies–as well as their contemporaries–are doing the best they can to keep up with, and maintain a slight lead on, the changes introduced by everyone else.
All of the admittedly revolutionary developemnts happened over a decade ago. Since that time Apple has increasingly turned to secrecy as a marketing tool. Microsoft however relies on a much more open hardware & software development & supply chain. There are public beta versions of all their upcoming versions of software so businesses can test functionality with their existing processes and test upcoming technologies. Instead Apple releases new hardware, says the software is on the way, and announces that the hardware will be discontinued in a year. Very different from a forecasting and system planning standpoint.
I smell bias.
Public betas are not definitive signs that a company is open with development. Public betas simply show that a company has a massive market for a product and they want to ensure that their product works well. It is also a spectacular marketing tool and a way to get early adopters. Quark, Adobe and Apple also offer beta programs.
It was only under EU rulings that Microsoft is opening more code.
Time always marches on. How can I get support for Windows 98? The only reason why Microsoft seems to be moving at a better (slower) upgrade pace is because it is a lumbering giant. That is both its asset and its weakness. No one is happy about whiplash development but we would be equally unhappy if we were still using Windows 3.1 and Mac OS 6.
Not bias, just frustration. I’m not looking for support of a legacy system. Just answers about how applications will run and perform on their current hardware and OS so I can make strategic decisions regarding IT investments. I’d like to go with the Intel Macs, espically after seeing some of the revised benchmarks that indicate the performance claims Apple made for universal applications seem to be accurate. But I have no way to know when that will be something I can buy. I’m frustrated that Apple has announced a fairly agressive (timewise) phase out of a platform before the software many users of that platform rely on has even been announced, released, or tested. I blame Adobe on this issue just as much if not more than Apple, it certainly appears that Apple made the developemnt tools available. But there really is not good alternative to running the CS regardless of platform.
Why does it surprise you that Apple is phasing out old machines before new software is ready? This is the 4th time they’ve done it, we should be used to it by now.
(6502 to 68000, 68000 to PPC, OS 9 to OS 10, and now PPC to Intel)
I agree that it is annoying, but it will always happen (and happens in the Windows world too. Try buying a new program for Windows 95 or even 98).
The big irony is that Intel is very forthcoming on their roadmap, and have outlined their plans for for the next 10 years. Apple won’t tell you what they’re doing tomorrow.
First of all I would like to say, great article. Though there is one point that sticks out in my mind that was not covered. When i think about Quark Xpress, Microsoft Office, and the Adobe Creative Suite, I remember that these products were almost all built pre OSX. Most, if not all of them contain legacy carbon code that does not work properly within rosetta. Not only that, but if memory serves me correctly, they were all built with code warrior, not Apple’s Xcode. Thus another roadblock in getting these apps out. I suspect that there is a great deal of code that is having to be redone in there products, and thus the long wait for an firm announcement.
Just my $0.02, take it for what you will.
Thanks, Paul.
I’m not sure about which of those apps were developed with code warrior or Xcode, so I don’t know whether to agree or disagree with you. I do believe that QuarkXPress 7 was rewritten and compiled to be a universal app, giving it native functionality on Intel-Macs.
Just read (warning: pdf link) from Adobe’s website. they do mention switching the entire codebase over to Xcode. I think that you are correct with QXP 7. From what I have read it looks as though they have been using Xcode and do have a fat binary of it.
Well that didn’t quite work… Anyways, here is the link:
http://www.adobe.com/products/pdfs/intelmacsupport.pdf
Pingback: Quark VS InDesign - » Adobe: No MacTel Photoshop Until CS3
Pingback: Quark VS InDesign - » Editorial: On the Subject of MacTel Compatibility…