Originally Posted by emig647
I was at both WWDCs and even in the sessions when Apple said they were going to support 64bit Carbon and the one where they said they weren't. When they said they were going to support it, they didn't have full commitment. They said they were going to try and have it by the end of summer. But in the same session apple was clearly explaining to devs that Cocoa was the future. I even remember Metrowerks asking about it at the time. Obviously they couldn't hit that mark. They never officially supported it, only said they were going to try. At the next year they even went over Resolution Independence, which is the technology that helps the move to retina. Sometimes things take longer than expected or don't happen at all.
Either way, as Melgross pointed out, without knowing the specific library that was pulled / changed, it's impossible to know if Apple gave warning or not. Regardless if they did, it's Adobe's job to keep up on this, not Apple's.
Apple's own software gets caught up in this as well. If Apple can't get their own software ready in time, how can we expect that third parties can get theirs ready in time? Look at how long it took Apple to get their own pro software to Cocoa, and 64 bits.
And Apple has had problems with removed Kexts and APIs with their own software. They also introduced bugs that affected just some software, and have taken some time acknowledging and fixing it. Often, not until a point update.
I'm not trying to put all the blame, all the time, on them. That's clearly not fair. But often enough, it is Apple. It seems to be impossible to release any software these days without some problem for someone.