No need to get philosophical when there are (as a couple of people have just pointed out) technical reasons for whether a port is practical or not. I'm disappointed that Macworld missed the second post that came from personal Adobe blogs, by audio app product manager Hart Shafer, because it gets into more of the technical reasons for the decision:
http://blogs.adobe.c...6/10/soundbooth[u]and.html
More commentary here on my site, including Chris Randall from Audio Damage (an audio developer) -- the programmers in the bunch, you'll notice, aren't surprised at all by Adobe's decision:
http://createdigital...for-soundbooth/
Basically, Soundbooth is an app full of exactly the kind of code that's hard to port between Intel and PowerPC processors. Just because Xcode can
compile for multiple platforms doesn't mean the code will run without adjustment, or (in many cases) run well. Part of Adobe's decision was based on performance, which is a good thing.
I understand the reaction of Mac users who didn't initially understand the decision, as I understand Adobe's reaction to getting slammed by hotheaded users. Ultimately, though, this whole discussion is largely a non-issue. This is Adobe's first home-grown audio app for the Mac platform (excluding Macromedia), and that's a good thing.
Also, note how open this discussion is. If this were Apple, we'd have no contact with the product managers and developers, and no Adobe Labs website with pre-release software, and no opportunity to give our opinions publicly on software long before a ship date. That means Adobe can respond to feedback about Soundbooth and what you think of it -- actual features, beyond decisions on porting to platforms. I'd love to have Apple occasionally open their process in the same way.