-dave-m- wrote in post #14825705
I could say it's just as much Apple's responsibilty to make sure software works with a new release. What is so different in Mountain Lion that a basic program like EOS Utility needs an update to work. Ever heard of backward compatability? Or is that forgotten because it's Apple?
As far as upgrading versions of Windows and software issues, sure they happen, but just as often you can reload old software with 0 updates needed. I currently have several programs/games that I have run on Win XP, Vista 32/64 and 7 32/64 with no updates or hassles. I have old peripherals that have not had driver updates since before Win 7 was released, but they work just fine with older Vista drivers.
It can be done, Apple just chooses not to.
I would mostly disagree with this. I understand there's a certain level of responsibility for the OS not to break certain things, but when a major new release comes out that introduces significant under the hood changes, changes that they're asking third party developers to comply with, the onus is on the third party to comply.
Of course, it can be a risky approach, as software development is not cheap and is time-consuming, and with a low Market share it can be easy for even the biggest companies such as canon to abandon the platform as it deems it's not worth the effort. I get that.
The thing with this situation is that eos utility actually works. It just won't work when plugged in with my 7d. But the 7d plays fine with Apple's stuff. So I suspect it's part of the sandboxing of apps that is breaking the communication of eos utility with the 7d. Argue what you will about sandboxing or something, but I still feel it's canons responsibility for their own software to work and not Apple's.
Is it canon's responsibility to make sigma lenses fully compatible on their bodies? If the firmware renders a third party lens from working, should canon be held accountable for it?