*Windows strength is compatibility, to get this there is some sacrifice in stability. Macs are less compatible with hardware but are more stable, you have to pick what works best for you.
I haven't seen some of these stability issues under Windows 7. I think we're all just pushing tired cliches
. Windows 7 64 bit does fine with large data sets assuming the hardware is appropriate for what you're doing. As an example you'll find a lot of complaints on AMD cards with Autodesk products under Windows with a couple Firepro exceptions. There are many things that Apple just doesn't support. Anyway much of the time it's just an issue of compatibility that has held a lot of people on Macs (myself included). In either case, Adobe products eat whatever ram you throw at them. I will say that while Windows has some irritating behavior too, I've encountered many wacom driver crashes with OSX. Those are always annoying.
Some of the family feud stuff between Apple and Adobe seems fabricated. As an example there wasn't much of a choice for Adobe with CS4. They even explained it in great detail mentioning they were waiting for Xcode to mature as it was still a difficult program for dealing with large software deployment. Adobe reversed their development plans once Apple decided to cancel 64 bit Carbon. This means 32 bit Carbon --> 32 bit Cocoa--->64 bit Cocoa rather than Carbon--> Carbon--->Cocoa. Adobe has different issues, but it's important to recognize that sometimes the reason we don't have a feature or something is lack of support from Apple rather than Adobe. This included a few cursor display issues in CS4 where they couldn't use the old thing.
Also note that it's not just Adobe. Pretty much every developer has stayed with an older OpenGL version. Supposedly the way Apple implemented it meant a resource prohibitive level of code updates. It's not just Adobe here. I can't think of one developer that moved on to the latest thing with Lion.