Quote:
it's entirely possible something in the final OS release will behave differently than the beta releases
Sure it certainly is possible but it's also a terrible excuse. An OS X point release could break everything as well and users are even more likely to upgrade to that.
Let's not forget Apple themselves have an investment in the ecosystem as well. The last thing Apple wants to do themselves is complete 180 on APIs from beta 1 to GM because that's more work
they have to do and support.
Quote:
With Adobe... they most certainly had resources and lines of communication available that smaller companies wouldn't have.
Many smaller, indie developers have had no problems getting their apps ready, either. Like I mentioned before, adequate testing is the only way to ensure things work. Usually after the first few betas Apple has things pretty firmed up. It's just disappointing that Serato waited until the very last minute—public beta—to even think about doing any testing.
I've always likened software and tech in general to jumping on a moving train. At some point if you wait long enough, you're going to get left behind, it's just a matter of
when to jump and that can make all the difference.
Especially considering Apple is billing this as more of a refined, maintenance release without that many features, users are going to expect that it's going to be a safer upgrade and go ahead with it (even if there are serious, under the hood improvements).
I understand the need to save resources but from a marketing and customer service side, you come off as a bunch of corporate bean counters. Which e-mail would you rather see from a company?
Quote:
"Sorry, our apps aren't ready for El Cap yet! We waited until the last minute to start testing so don't even try using them yet, there's serious compatibility issues."
OR
Quote:
"We're all ready for Apple's newest OS! Yup, ready on day 1. Come to our website, grab the new release, and buy another set of control vinyl while you're at it..."
