5 ms·

Not true, as the iPhone gets more popular, Adobe will take care of those custom features. Adobe's history of failing to update their products to take advantage

Not true, as the iPhone gets more popular, Adobe will take care of those custom features. Adobe's history of failing to update their products to take advantage of OS X, of Intel processors, of Cocoa, or of the Mac platform entirely seems to give to lie your belief.

sorbus 17y ago
But someone else could have.
vetinari 17y ago
How is that? In 2001/2002, the way to move your code base from Classic to OSX was Carbon, not Cocoa. The switch to Intel was another big porting project. Now, if they want to switch to x64, they will be also forced to switch from Carbon to Cocoa. So in few years, Adobe had to port their codebase several times to meet the OSX moving target. Actually, I'm suriprised they did it at all, considering the lack of transparency on Apple side. If you are asking Adobe to throw away any frameworks used, that were later duplicated by Apple in OSX, and port to Apple provided frameworks, you have no idea how the project of the Creative Suite size is managed and developed. You may port your little OSX-only utility fast, but not CS. Other big projects had similar problems - Microsoft Office? Alias|Wavefront (today Autodesk) Maya? They have similar pain points for the exactly same reason.
- danudey 17y ago
  The thing is that yes, these were all pretty big porting projects, but they were also things that Adobe would have known about years in advance, and just never bothered to deal with until after it was an issue for most people. When they knew about an upcoming platform change a year or two in advance, and didn't bother to deal with it until a year or two after, I have to assume that they just never cared. That's why Apple doesn't want to deal with Flash - they don't want to rely on a company that doesn't care about Apple or its users, and they don't want to be beholden to Adobe's schedule of 'we'll support that next year when users are hurting for it'. When Apple announced location support in iPhoneOS 2.0, for example, including GPS for the iPhone 3G, would Adobe have had it ready for launch day? From their history, Flash would have waited until the next 'major release'. Flash-based apps would have had a reduced feature set, and the App Store would have been full of applications that couldn't support the latest and greatest features, distracting from applications that properly supported 2.0 from the start.

sorbus 17y ago

But someone else could have.

vetinari 17y ago

How is that? In 2001/2002, the way to move your code base from Classic to OSX was Carbon, not Cocoa. The switch to Intel was another big porting project. Now, if they want to switch to x64, they will be also forced to switch from Carbon to Cocoa. So in few years, Adobe had to port their codebase several times to meet the OSX moving target. Actually, I'm suriprised they did it at all, considering the lack of transparency on Apple side. If you are asking Adobe to throw away any frameworks used, that were later duplicated by Apple in OSX, and port to Apple provided frameworks, you have no idea how the project of the Creative Suite size is managed and developed. You may port your little OSX-only utility fast, but not CS. Other big projects had similar problems - Microsoft Office? Alias|Wavefront (today Autodesk) Maya? They have similar pain points for the exactly same reason.

danudey 17y ago
The thing is that yes, these were all pretty big porting projects, but they were also things that Adobe would have known about years in advance, and just never bothered to deal with until after it was an issue for most people. When they knew about an upcoming platform change a year or two in advance, and didn't bother to deal with it until a year or two after, I have to assume that they just never cared. That's why Apple doesn't want to deal with Flash - they don't want to rely on a company that doesn't care about Apple or its users, and they don't want to be beholden to Adobe's schedule of 'we'll support that next year when users are hurting for it'. When Apple announced location support in iPhoneOS 2.0, for example, including GPS for the iPhone 3G, would Adobe have had it ready for launch day? From their history, Flash would have waited until the next 'major release'. Flash-based apps would have had a reduced feature set, and the App Store would have been full of applications that couldn't support the latest and greatest features, distracting from applications that properly supported 2.0 from the start.