I don't really blame either side when it comes to things breaking like this.
The OS vendor has every right to release new features, and while it would be nice they surely can't test all software.
The software vendors often have to react, which is unfortunate but understandable.
However, where they could improve in many cases is timeliness.
The Captivate example is perfect - why is this still a 'hot fix' and not an official update?
Meh
We don't either, Erik, mainly because we have no idea who to blame.
In the early Mac days (1985 to 1993) Janet & I had a regular parade of studio owners coming through our studio asking a plethora of technical questions. We'd frequently hear, "We got the upgrade to ___ (insert name of Adobe app) ____ and now the ___ (insert name of feature) ____ won't work." Better than 90% of the time they had a 3rd party plug-in which needed to be updated but no update had been made available.
The point is that the end user launched a new version of an Adobe app, something didn't work, it's Adobe's fault.
If we told people to disable a favorite filter or how type was displayed, we had the wrong answer.