As to your assertion that "Adobe does this once" have you so soon forgotten about Aldus Corp and Macromedia.
Well, is a merger a buyout? Yes, some of Aldus's portfolio of apps were discontinued but the flagship apps of PageMaker & After Effects are still developed and sold by Adobe. Freehand was sold to Macromedia as part of an anti-competition settlement. Ironic that Freehand ended up at Adobe after the Macromedia merger and has not been developed further.
But Adobe didn't do those mergers to kill competing products otherwise they would have killed PageMaker & After Effects. They merged with those companies for sound business reasons and these mergers were not hostile takeovers. Many of the officers and employees of Aldus and Macromedia ended up at Adobe and formed the core of much of the app development going on now.
The latest issue regarding mac printing had Adobe initially pointing the finger at others when the problem was theirs. Are you optimistic or are we watching the gradual demise of a company known for great, reliable, ergonomic products?
Well, the coding errors that were caused by Apple's yanking API's were Adobe's fault...but even Andrew and Mark would have to admit the bug was subtle and difficult to detect. Yes, somebody screwed up...they got called out, outside users proved the problem, they then admitted the problem and fixed it for Lightroom really, really fast (a lot faster than I was expecting) and will fix Photoshop in the next update.
Would I have preferred the engineer/s didn't screw up the print pipeline on Mac? Yes...am I surprised that it was a move by Apple to force all developers to change the API's they were successfully using until Apple made them change? Nope, not at all. This is far from the first time something Apple didn't screwed over Adobe and it's user base. As Andrew will tell you, Apple has continuously screwed over developers many, many times and over and over.
Was it Apple's fault that an Adobe engineer screwed up the code? Nope, but it was a code change that was forced by Apple. So far, I have't seen Apple implicated in this problem much, only Adobe. Note, Windows users have been blissfully printing away without this issue.
You all can keep harping on the mistake and ignore that facts and fail to enjoy the bug fix Adobe rushed out the door...in the meantime, I'm pleased I can now print out of Lightroom again :~)