Reprieve for Booting New Macs With Mac OS?
MatthewRothenberg writes "Apple has announced that as of January, new Macs will boot with Mac OS X only, but now MacInTouch reports that there might be a reprieve in the works for booting with Mac OS. According to one reader, a Quark representative has been calling pro publishers to ease their worries about the lack of a Mac OS X-native version of its QuarkXPress DTP program; after talking it over with Quark, Apple has agreed to move back the Mac OS X-only deadline until June." I can imagine that conversation with Jobs: "Why don't you just finish porting your freaking product already?"
I bet the program was filled with a bunch of coding tricks that made Classic Work Fine but those tricks no longer work in OS X. Although a lot of the framwork may be simular the reality of coding is sometimes inorder to get it to work the way you want you will need to do some tricks that makes porting harder. It is my guess the code it well hacked up and they are running into a lot of stumbling blocks in order to get it to work.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
For many many years Apple bent over backwards to allow legacy software to continue to work, through the transition to 32-bit addressing to PPC and so on. That has started to break down in recent years, and while I can appreciate the benefits of things like abandoning the 68K machines with new OS's (speed, for example), and now, to a lesser extent, booting into OS 9, I'm worried Apple may get a little too used to it, as Microsoft long has been. These moves are a great tool to force people to upgrade ... and Macs users reasonably get pissed over being forced to upgrade -- hardware or OS or apps. The easy path of abandoning compatibility makes more money for Apple, but sacrifices an element of the OS that many of use consider really, really important.
... I've felt that Microsoft has manipulated its profits and bug-fix burden for years by telling users to "get an upgrade" ... Apple may drift in that direction to its long-term detriment ... and yes, before anyone leaps forward, this is an obvious chip in favor of the free software movement. I'm just heavily invested in the older ways; yet (Steve? Are you listening?) I certainly don't rule out moving on. We're not at that crossroads, but I don't like the signals I glimpse ahead (hey, I maintained a metaphor.
I adopted OS X well, but was still have uses for OS 9, as on our iMac. The OS X was a novel transition for me, as a 15-year Mac user, because for the first time I had to upgrade several apps to work under the new OS (Classic Mode is not a panacea!). When Apple starts to disconnect from the legacy machines, the software publishers will also do so, if only because maintaining different versions for different machines is too onerous. But many of us have funky old programs that will never ever be updated because their authors have moved on, or the upgrades offer nothing we want to pay for -- we just want to continue on as we have. That won't be possible for long, esp. if the hardware path abandons our antiquated (read: 3 year-old) ways.
Concretely, I first heard about this from the IT guy at my kids elementary school, which has a substantial flotilla of iMacs. He said it was going to be a pain for them, and with PC forces already snipping at the Macs -- the school admin and high school computers are PC's -- this could portend bad stuff for Mac land. It is a fact of life that the schools buy buy new machines to replace broken ones or expand, and if that necessary path is suddenly encumbered by new transitions and expenses, well, some places will decide it is an opportune time to homogenize the fleet.
Just some musings
Assuming you're not just kidding ... :-)
QuarkXPress has long been the Big Kahuna of page-layout packages (after overtaking Aldus' pioneering PageMaker app back in the early '90s).
Professional publishers have invested billions of dollars into desktop workflows built around the Mac and XPress and involving all kinds of software plug-ins required to make all the hardware and software in a publishing operation work almost seamlessly. (Older versions of those plug-ins won't work with a Mac OS X version of XPress.)
Publishers are very conservative about making sweeping technological changes, but the whole shift to Mac OS X is ultimately going to force them to make some serious choices -- especially if there's a serious temporal disconnect between the arrival of Mac OS X-only Mac hardware and a Mac OS X-native version of their centerpiece software application.
Once you fold in all the imaging peripherals, client-server solutions, fonts, graphics applications, color-calibration technologies and whatnot, it's a wonder that stuff gets published at all. And when you're trying to use the same content for various print and electronic media, it gets even nuttier.
Even in these tight times (maybe especially in these tight times), there's a lot of money riding on keeping the whole house of cards stable, and the prospect of some sort of disjunct between publishers' longtime preferred platform and their longtime killer app is daunting.
Everybody seems to forget how expensive the transition to OS X can be. Some of our design customers have many workstations, ranging from old 9600's (8100's even!) to modern G4's. NOBODY is thinking of getting rid of all the old stuff and putting modern OS X running G4's in their places. Heck, some of these machines are still running 8.1 or even 7.6.1! The only thing I see happening is that some new machines run OS X "to test the new system". And even that is quite an investment. ATM doesn't exist anymore so a Suitcase has to be bought. Other programs need to be updated (Photoshop, Illustrator, Office or MacLink, VPC). Sometimes the company's servers have to be upgraded as well (under OS X the FileMaker and Retrospect clients only do TCP/IP, Retrospect 5 doesn't do any AppleTalk anymore forcing an upgrade on other older machines). And the customer has to be taught how to cope with the new OS. Everything is different! Count out the hours, the upgrades, the production time lost. This (OS X) is a huge investment. Some customers are wondering if it's all worth it at all. We've been telling them it's not worth switching to PC's for the same reasons, and now they have to move to OS X which is almost just as much work.
So it's a good thing Apple's trying to force us. But it may be quite a pill to swallow for some. And I think "Classic" Mac OS machines will be around for some time to come.
BTW: Personally I LOVE OS X. I'm never going back.
Apple's Education customers probably had some small part in this, too -- I screamed at Apple pretty loud saying we weren't ready, and they replied that we should buy our next year's machines by January.
Never mind that our next budget year isn't 'til June.
I think this will allow schools to make one more year's worth of purchases that are still OS 9 compatible.
One more year of OS X's maturation (both client AND server) will really really help schools make the transition.
(Not to mention we have to save our pennies and budget for new versions of Office, PhotoShop, etc., since we don't want to buy more RAM to run X just to use all classic apps...)
I'm still having bad dreams about how we're going to train everyone to use OS X, or how a mixed 9 and X environment will work.
(I don't care how flawed it was, people will MISS that darn old Chooser)
- Peter
INsigNIFICANT
Both Cocoa and Carbon *are* native APIs. There are ways to tell what kind of app you are running though. If it starts up Classic and you see non-Aqua windows, then its not native. If you do a Get Info on the app and see a "Open in Classic Environment" checkbox, then its Carbon. Note that is still a native app. If you right-click on the app and see "Show Package Contents" in the contextual menu, then its either a Cocoa app or a Carbon nib-based app. I'm not sure how you can tell the difference between the last two types short of attaching gdb and looking, but there is probably a way.
I'm hoping that they push back the non-booting computers indefinitely. A computer that can't boot 9 is a computer that can't boot from a CD, at least not usefully. The OS X install CD boots straight to an installer when you boot from a CD, and doesn't let you access any kind of file manager. Until someone comes up with a way to boot into a file manager in X from a CD, stopping booting from 9 is a bad idea.
The sooner the educational market switches to OSX the better. I've been using Classic since 7.5, and one thing I didn't like about it is that stuff learned about the Mac OS was non-transferrable. You can learn to hack with ResEdit and write Applescripts and have fun on a Mac, but those skills were useless on any other OS. I always felt like if you want to get your hands dirty, you should run *nix. I knew Windows pretty well in high school, and when I got to college, I didn't even know what Unix was. Now we've got OS X. If you train kids on OS X, they'll be ready for any computing direction. If they go into a computer science field, it'll be an easy transition to a Unix or Linux box (not that they couldn't use a proprietary OS). If they become designers, audio engineers, or digital video specialists, they'll already know the most used OS. If they just want to be Sales Monkeys or gamers, well, they'll have to learn Windows.
It's not an issue of how flawed Classic was. What's important is that OSX is built on rock-solid open technology, the same that is being used on the world's best servers and workstations. I just got OSX a short while ago. Pretty soon, I'll be figuring out how to run a cron job. That knowledge is not Mac-specific. It's general computing knowledge. I like that.
c-hack.com |
You know, Quark has eschewed Mac standards for as long as I can remember. They're UI was (is) totally proprietary, and their key shortcuts are a pain to figure out. Learning Quark was about as easy as learning a whole new OS. I always got the feeling it was totally hacked together. Maybe if they'd spent a little time making their program more standard, they wouldn't have this problem. I have no sympathy.
c-hack.com |