Lightroom to join Creative Suite in going Intel-only
updated 10:40 am EDT, Fri August 14, 2009
Lightroom going Intel-only
Lightroom, Adobe's workflow tool for photographers, will officially join other programs from the company in going Intel-only. The announcement follows a similar one for the Creative Suite, revealing that its PowerPC support will be phased out in a manner reflecting the switch in Mac OS X Snow Leopard. Apps in the Creative Suite include titles like Illustrator, InDesign and Photoshop.
While the next major upgrades of Lightroom and Creative Suite will not have PowerPC compatibility, Adobe does note that support will continue for existing software. Updates should be relatively limited though, addressing only "critical issues" as they arise. Adobe has not yet hinted when Lightroom 3 or Creative Suite 5 might ship.












who cares....
08/14, 11:35am reply
...what I care far more about is if Adobe will finally use the Package format for their installers, and if the application will finally be 64-bit, or if they come up with another lame excuse...
ZinkDifferent
Fresh-Faced Recruit
Joined: Jan 2005
The problem is...
08/14, 04:52pm (1 reply) reply
Two things hinder Adobe from being a great company with great software (like they once were):
1) Being tied to a single base code for both Windows and Mac generally doesn't allow them to take advantage of Mac only technology (or Windows only tech for that matter). So while Apple makes great tech cores available to developers, you hardly ever see Adobe take advantage of them because they're not available to the Windows side.
2) Who's competing with Adobe? Maybe that's the real problem. If there was a major threat to Adobe, maybe they'd innovate more?
Really, CS3 and CS4, while they were decent evolutions, didn't really address the disparity in how the apps work the "same". For example, placing an image in InDesign is still different than placing an image in Illustrator – why? CS4 has made some progress towards fixing this, but come on! They keep trying to sell this, but never fix it.
That's just my 2 cents...
rvhernandez
Fresh-Faced Recruit
Joined: Apr 2005
Re; the problem
08/15, 03:12pm reply
Being tied to a single base code for both Windows and Mac generally doesn't allow them to take advantage of Mac only technology (or Windows only tech for that matter). So while Apple makes great tech cores available to developers, you hardly ever see Adobe take advantage of them because they're not available to the Windows side.
But being tied to the same source allows adobe to make feature-compatible versions of their software for both Mac and Windows, as opposed to many a Windows program whose Mac versions are lame and a poor substitute.
On top of that, these great 'core's apple has that you bemoan them not using aren't anything their apps didn't already have.
Let alone the concern that, if they did use Apple's core technologies for some of their image routines, the results you get off the Mac might be different than running the same routine when on Windows. Having a single base allows for those to work the same.
LouZer
Fresh-Faced Recruit
Joined: Nov 2000
64-bit
08/15, 03:14pm reply
Well, maybe if Apple didn't drop the Carbon 64 project, Adobe would have already had been out in 64-bit. But no, Apple decided to, once again, leave developers off in the lurch and Adobe now had to rewrite their software to Cocoa.
Then again, maybe one day Final Cut will be Cocoa and 64-bit as well....
LouZer
Fresh-Faced Recruit
Joined: Nov 2000
re: re; the problem
08/17, 02:38am reply
@LouZer
Except that it's not the case with Adobe. They have a lot of feature disparity in Acrobat, Flash, Premiere .....
You would think that would be the case ... but it's not. The only reason they share a code base is because of the dev environment and toolchain - in Adobe's case it's Qt.
shawnde
Fresh-Faced Recruit
Joined: Apr 2008