Agreed. Is there some kind of hidden rule I'm not aware of where Apple can do no wrong and it's everyone else's fault when something goes wrong? No person or company is perfect, everyone and thing is entitled to make bad decisions and judgments.
True, its Apples fault, except there is a huge cost in developing two API's (and making sure you get everything right), so they could get rid of Carbon they had to get rid of something big, in this case 64 bit support.
But Adobe already knew they would have to rewrite it for Windows and started on it appropriately. And even then going from Carbon to Cocoa requires learning a whole new API and changing your style of programming compared to going from a 32 bit to 64 bit Windows API. The fact is that Apple told them late and Adobe are trying as hard as they can.
I think that is probably fair. They should have dropped Carbon at WWDC 2006.
Having programmed in both Mac OS and Windows I definitely see SOME similarities between Carbon / Cocoa and Win32 / .NET. For example with the latest features: in Windows, WPF is designed to be used with .NET and in Mac OS, Core Animation is designed to be used with Cocoa.
I haven't used Win32, but honestly .NET is much worse than Cocoa. Microsoft's API's do suffer from the weakness that they never make a hard decision like this, which really makes them much worse than they should be. Apple is right to kill Carbon, and Adobe was right to stick with Carbon as long as possible, its just difficult for both of them now.