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.
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.
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.
Are there examples of this happening consistently in other cross platform development environments? My understanding is that cross platform frameworks cater to a lowest common denominator among platforms, perhaps occasionally supporting a custom feature here and there. Even then, the people developing the app need to spend the necessary effort to take advantage of platform specific features, as opposed to just deploying the identical app to all platforms.
Of course you do, developing with Flash on OS X is infeasible, the performance is laughable and the stability is worse (like the article says, Adobe's been neglecting Flash on OS X since forever).
You have to use Windows to get any work done, and that is just as "specific" as having to use OS X.