Even if the headline was accurate instead of hyperbolic, my response would be something along the lines of "because no one's a fairer and more impartial judge of Apple software than Adobe." That list of incompatibilities is something I think Adobe should be ashamed of: it is essentially a "List Of Areas Where We Don't Have Our Shit Together." Apple's cut-off dates for legacy versions are pretty aggressive, true, but with the notable exception of the XServe (and how many people do you know running Creative Studio on an XServe?) they're also aggressive about announcing them ahead of time.<p>This is basically another data point in the pattern of Adobe not being a very good development house, along with all the points about "please exhibit good design taste in your design applications."<p>Then there's this:
"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.""<p>That's not a "woe," that's "repeating Apple's documentation of the feature."
In case you want to skip The Register's hyperbole: <a href="http://kb2.adobe.com/cps/905/cpsid_90508.html" rel="nofollow">http://kb2.adobe.com/cps/905/cpsid_90508.html</a>
I think it's worth keeping in mind that even Microsoft as of Office 2011 has excised all the PowerPC cruft from Office. Adobe has no excuse other than laziness. The fact that people defend them and attack Apple over this floors me. How long would it have taken to get all the PowerPC code out of CS if Apple didn't have such aggressive cut offs?<p>I also love that people think Apple needs Adobe more than Adobe needs Apple. Take another look at the revenue for each company and the percentage of Photoshop users on OS X and THEN try saying that with a straight face.
<i>"Java Runtime needs to be installed manually, otherwise applications may behave inconsistently"</i><p>OS X asks you and automatically downloads it when an app requires java, this happened soon after my first boot up with lion<p><i>"Files stored in Library"</i><p><i>"Scrolling behavior opposite of expected"</i><p>These are not 'issues', this is by design.<p><i>"Rosetta support no longer included with Lion"</i><p>This was known way before wide release of Lion, no reason for Adobe to be unprepared for it.
The real story here is: "How long will it take Adobe to bring their products up to speed".<p>Not that I'm saying they wont, and it's good that they're proactively documenting the incompatibilities between their products and Lion<p>That said, based on Adobe's history with Apple and OS X, and the fact that Adobe has used Flash support in iOS as a pro Adobe/Anti Apple PR tool, it's reasonable to expect them to drag their feet with this stuff.
Should I start a list of my Adobe software woes?<p>I mean, seriously -- even the frickin' keyboard shortcuts don't work in AIR "apps". And don't even get me started on the whole "updater" thing.
Pixelmator works well on Lion:<p>"<i>Ready for OS X Lion
Wednesday, 20 July 2011. Posted by Saulius.<p>I’m very happy to let you know that while working extremely intensively on Pixelmator 2.0—codenamed Chameleon—we still managed to improve the currently available version’s compatibility with OS X Lion. Pixelmator 1.6.6 adds fixes and improvements that will help the app run smoothly on OS X Lion.<p>Lion is a must-have upgrade of Mac OS X. Believe me, we spent a lot of time using it, and everyone at the Pixelmator Team absolutely loves the OS X Lion.<p>To easily update to Pixelmator 1.6.6, simply use your Mac App Store app. For non-Mac App Store users, it is highly recommended to transition to the Mac App Store at this time. However, if not ready to transition yet, users can run the Software Update feature in Pixelmator.<p>High-end support for OS X Lion is coming along for Pixelmator 2.0 Chameleon. With Lion-specific features, the new version is going to totally rock on OS X Lion. If you haven’t yet noticed, we have a sneak preview website for more info about what’s coming in Pixelmator 2.0.<p>And finally, we thought you might be happy to take a look at the new Smudge Tool in Pixelmator 2.0. Enjoy the video!</i>"<p>(from <a href="http://www.pixelmator.com/weblog/" rel="nofollow">http://www.pixelmator.com/weblog/</a>)
Considering the premium price of the Adobe suite, it's fair to expect premium support. Hopefully Adobe will get their software sorted at least as far back as CS4.
So, the complaints seem to break down into two types:<p>a.) things which broke because they depended on Rosetta (PowerPC emulation), when Apple has been warning for at least three versions that PowerPC emulation will be going away any version now.<p>b.) things which Lion makes available to apps (new APIs), but which Adobe apps don't yet use -- meaning only that their apps work as they always did, but don't take advantage of new features of Lion.<p>Depending on the length of Adobe's release cycle, they may not have had enough time to prevent b.) since developer previews of Lion became available earlier this year -- but they can't really claim they didn't see a.) coming.
If I remember correctly, it took forever for Adobe to port to OS X in the first place, and even then, they were running on Carbon for much longer than a lot of other major apps. It sounds like they have a really hard time letting go of legacy code.
I've had so many issues with Adobe on Windows and Apple platforms over the years that I'm not at all surprised at how this played out. I've long abandoned Reader in favor of the FoxIT version for Windows and Apple's Preview. Adobe seems incapable of implementing a competent quality control program.