|
... and it don't work like that. ANY large company, be it Apple, be it Microsoft, etc, will make every possible effort to maintain compatibility. BUT it is unreasonable to expect the company providing the OS to do regression testing on all third-party code, as there are literally thousands of applications out there. The best they can do is inform the developers that stuff is being rearchitected, and provide pre-release versions for the third party vendors to use to test their stuff. If problems were found, the vendors can get back to Apple and say, this doesn't work with my stuff anymore, and a determination can be made whether Apple needs to change something in their code, or if the third party product wasn't using QuickTime correctly anyway.
Third party software companies are quite often rather lax in testing their software with new OS versions. As I said in my earlier post, developers get these things months in advance, there is little excuse for not testing with upcoming versions. I found some issues with Quicktime's font handling in Windows a few months ago, when testing a prerelease of a new version, and how it worked with my software. I got Apple on the phone, and had the issue resolved almost immediately. Because I KNOW shit happens when new versions are about to be released, I make sure the stuff doesn't break my code, and if it does, I know I can contact the engineers and get the problem resolved, or get a work around.
Apple also provided a QuickTime 7 un-install that would remove the thing and put QuickTime 6 back, should it be found that the third party software has not been patched to work with the new QuickTime version.
Macromedia should have tested their shit and gotten a patch out prior to QuickTime 7 being released, like any LARGE and responsible software company interested in not pissing off their customers would have done, especially in light that Apple had the betas for this stuff available for third parties to test with their software some 6 months prior to release.
|