Slashdot Mirror
Adobe Universal Binaries... in 2007
bo peterberg writes "According to a pdf on Adobe's website, they remain committed to supporting Intel-based Macs. However, Intel-based Macs will not be supported until the next upgrade of all creative products. The current version will not be re-released."
The first IntelMacs use 32 bit CPUs, but Intel will release 64 bit version of the CPU later this year. Will these first IntelMacs be obsoleted? OS X for the Intel CPUs will obviously go to 64 bit --- need it for the PowerMacs as their power users won't want to lower memory capacity. Maybe Adobe and other third party software vendors see this situation and prefer to just wait and do only 64 bit Intel native binaries?
There are no real surprises here. This is very similar to how they transitioned Photoshop and Illustrator to Mac OS X several years ago. My main hopes are that CS3 is not living half in two worlds like they did with Illustrator 10 and Photoshop 7.
On the bright side, if Adobe keeps up the status quo on Creative Suite 3 then we will see all of the Apps that ship in Creative Suite, ship together. Acrobat 5 was horrible on Mac OS X, the Acrobat application ran natively in OS X, but the distiller ran in Classic and suffered severe performance penalties as a result. Hopefully all of the apps tranistioning around the same time will leave a better taste in their customers mouths.
I am glad to see them attempting to show off their xCode developemtn prowess by delivering the LightRoom beta earlier than their other software packages.
So much for LightTable destroying Aperture!
Actually, LightTable is the exception. They announced they will have a beta of it available shortly. Now if only Apple would release a competitor to Photoshop, Illustrator, and Framemaker maybe they'd come out with new versions of those products as well.
It would be unwise for Apple to release a photoshop competitor. Look what happened to the Mac version of Premier when Apple released Final Cut Pro...
You mean when Adobe killed it and most of the users migrated to Final Cut Pro, making Apple a lot of money?
Even after I knew the Intel Macs were coming, I chose to invest in a Dual-Processor Dual-Core G5. Why throw money at the platform that is guaranteed to be phased out?
:)
I worked through the transition from 680x0 to PowerPC. I worked through the transition of OS 9 to OS X. These transitions are NEVER easy. I chose to get the most power I could out of the platform that currently works best. I'll wait to get an Intel Mac until they are well into year two of general use, and only after my must-have applications have had at least one set of bug fixes released to their Universal Binary versions.
-Chris
-- This sig is only a test. If this were a real sig it would say something witty. --
I work on plugins for Adobe's applications occasionally, and let me say that the [apparent] "maybe in 2007" statement from Adobe is not a big surprise to me. The applications in their creative suite and plugin software development kits rely on CodeWarrior, which is [effectively] a dead product. AFAIK, it could never support development of universal binaries, and I would speculate that they have known this for a while.
Adobe's plugin Software Development Kits (SDKs) are based on C++ object models, which will mean that plugins and their host applications will need to be built with the same tools for everything to work. To move on, I think Adobe is going to have to move all their products and SDKs to XCode (gcc), and though I do not work for Adobe, I would wager that it will be a fairly tough job. IMO, Q2 or Q3 2007 seems a fairly realistic goal.
The problems the Intel transition will pose for both Adobe and the third-party plugin developers will be daunting. Quark and its associates have similar troubles, but I have personally seen some decent progress on the Quark side, though I think NDA prevents me from saying anything specific. Though I have seen little progress from Adobe as yet, I am confident they will deliver.
Adobe has a lot of work ahead of them, so I would encourage users of Adobe's creative apps to be patient, and realize how much work Adobe has ahead of them and that it involves more than just moving the applications to Intel. SDKs often offer as many if not more challenges than their host applications. I will part with a criticism: Everybody has known that CodeWarrior is dead for a long time. I think Adobe should have started putting more resources into jumping ship right when the writing went on the wall. Now we are all going to have to wait a while because Adobe was so shiftless about getting off the dead branch.
That's not quite what happened...
Premiere was not discontinued for Mac until well after Final Cut's launch. Apple basically stole the entire market from them. When sales fell through the floor, Adobe discontinued the Mac version of Premiere, and also announced that basically all of their software should be run on PCs for best results, a historical first. This was essentially the beginnings of the major Apple/Adobe rivalry. (They were really pissed about iPhoto as well.)
It doesn't get mentioned a lot around here, but Premiere was hardly the only Apple casualty in that space; they have virtually eaten the nonlinear editing space in a very short span of time. Remember Avid? They are still around but not nearly the force they once were, a name pretty much synonymous with high end / cinema nonlinear editing. Media 100 also. Final Cut is a juggernaut, a totally killer app. And Apple has Final Cut Express to compete with as well. And then they picked up Shake and RAYZ and a few others to eat a piece of what SGI used to totally dominate.
The really funny part is, Final Cut started its life (as I know the story) at Adobe, as a radical new verison of Premiere after v4. Premiere 4 was super popular, but people who know it and used it will all tell you that v5 sucked big time. The reason for this is, the Premiere team had this great new interface but Adobe didn't want to deviate so radically from the old Premiere look and feel. In frustration a large number of them quit and went over to Macromedia, who started developing their own editing app called Final Cut. It evolved for a bit there, but Macromedia got cold feet and had a sort of had a truce with Adobe at the time, so they sold the unreleased codebase... to Apple.
(This is hearsay I received from a high mucketymuck at Adobe who was bombed on Bailey's at the time, so take as you will.)
If Jesus wants me it knows where to find me.