Adobe releases lengthy list of Apple Lion woes
19 apps with foul-ups from fatal to decidedly annoying
One day after Apple's Mac OS X Lion was released into the wild, Steve Jobs' bête noire, Adobe, has released an extensive list of wounds that the big cat has clawed into its products.
The appropriately titled "Known Issues with Adobe products on Mac OS 10.7 Lion" is a 1,500-word litany of woe, listing Lion-caused problems in 19 Adobe apps, and calling out some non-app-specific basics such as the need to install your own Java runtime and how to find your username/Library folder, which Apple has chosen to disappear.
Problematic apps include such stalwarts as Photoshop CS3, CS4, and CS5; Dreamweaver CS4, and Illustrator CS5 and CS5.1. Problems range from mild, such as multiple keychain entries for Dreamweaver CS4, to fatal flaws for some features, such as the disabling of Droplets in Photoshop.
Droplet death – which is fixable in Photoshop CS5 through an update, but not so in CS3 or CS4 – is due to the fact that Lion no longer includes nor supports Rosetta, the dynamic code-translation tech that let old PowerPC code run on Intel-based Macs. The code that enabled Droplets, it seems, was written for PowerPC, and was upgraded only for CS5.
Adobe also notes that one of Lion's marquee features, the System Preference that allows you to have Lion restore an app's windows just as they were when you quit that app, doesn't work at all in Adobe products. "This feature requires new code in order to work properly," they note. "Adobe will research adding this functionality for inclusion in future versions of our products."
Not that this last bit is any great surprise. As Leopard and Snow Leopard users will tell you, Adobe software such as Photoshop never did play well with those operating systems' virtual-desktop feature, Spaces. There's apparently some under-the-hood incompatibilities with Adobe's window handling and Mac OS X.
As with all operating system upgrades, incompatibilities arise with previously trusted apps – especially apps with ancient chunks of code still lurking inside, such as Photoshop and other Adobe offerings. ®
I would love to know Adobe's excuse for not having identified and fixed all these problems long in advance of Lion's release. It's not as if Adobe couldn't have gotten a pre-release version to test against. For things like Photoshop, I can understand the testing difficulty of re-testing such a monolithic application, but the flash browser runtime? C'mon...
For the amount of money that they charge for their products, their level of support is embarrassing. The fact that they are still using PPC-only code in something as recent as CS5 is flat out incompetence.
Re: Wouldn't it be nice
If Adobe used standard OS windows and controls etc like *every* single other mac app on the platform so these problems, which are so common there's a website dedicated to pointing them out, didn't occur in the first place.
Fixing this is non trivial, seeing as it involves rebuilding the entire UI of the CS Suite, but then rolling their own UI was Adobe's choice, as was sitting on a Carbon codebase for a decade after it was depreciated. Numpties.
To the point, wouldn't it be nice if Adobe hired some engineers that can code worth a damn.
EXACTLY. Completely agree.
Adobe software has never supported the standard Apple install process either.
ie drop into Applications. They have always hidden away all sorts of crap all over the place.
If you have any trouble with an install - then you're shit out of luck trying to find every last little piece before you can try to install from scratch. Especially since the uninstall option *doesn't*.
Fecking stupid Adobe. They have had plenty of time to make their software play ball.