Adobe's Responsiveness to 10.6 problems

Question

I thought I'd start a thread just for the discussion of Adobe's responsiveness to the problems some are having with CS and SL.  There is too much hijacking of threads with rants going on in threads in which users are sincerlly looking for techincal help and users are sincerlly trying to offer techincal help.
So, to begin I just wanted to point something out to some of the "now now now" people screaming about crashes.  Snow Leopard was offically released Friday.  Whatever bug reports came into Adobe came in over the weekend.   I havent' seen the crashes, but depending on the crash they may not of even gone to Adobe, but gone to Apple instead.  Regardless assuming Adobe is getting them through thier crash reporting, they've hadall of 2.5 bussiness days to work on this.  Not all, but many people these days seem to think that companies can react instantly to things like this.  As if they have 60 employees standing by with nothing else to do but jump on the latest fire. That's simply just not realalistic.  If you wanted that you'd be paying thousands of dollars for your software, not hundreds.
Regadless companies these days are WAY more responsive these days then they were years ago, but we're still a long way, maybe even an enterinty away, from the responsiveness some people seem to expect.
I have to reiterate that if you installed SL and CS on a machine you use for your livelyhood without testing it yourself you need to learn a built about best bussiness practices.  It's your own damn fault.  Witness the self-loathing fools who write things like "I should have know better", well yes YOU SHOULD HAVE KNOW BETTER.
Dear Adobe, I expect a fix for this in the coming weeks...  hopefully by October 1st...  that seems reasonable...

Answer 1

It's slightly worse than you think:    reading crash reports and making sense of them is a lot like reading assembly language.  There aren't many engineers who can do it, and it takes time.      That being said, I've just spent the first 3 days of this week reading and categorizing crash reports.
That's time I should have been spending on features.
But frequent crashes aren't a good thing and need to be investigated quickly.