@Tom2181831781xv said: do you work for adobe? if not pelase don't reply.. I'm waiting for an offical response...your opinion is noted but I am looking for facts
This is a user-to-user forum. I don't work for Adobe but here are the official facts.
And here is my opinion:
One of the main reasons for having an OS is to interface with the computer hardware so that software like Elements will work on it. Elements 2022 has been out in the wild for more than a year before Ventura was released. Apple had ample opportunity to test whether that version (and indeed all prior versions) would work on its new OS. As has been mentioned, Apple sells Elements in its store, so I'm sure it has an extra copy or two laying around for its engineers to test. Now, users are finding that Elements 2022 (and presumably all prior versions) do not work with Ventura. What conclusions do I draw from this? Either Apple engineers are incompetent (which I think is unlikely) or Apple really doesn't care about providing OS support for legacy products of its competitors. (Yes, Adobe is a competitor of Apple and, in the past, the relationship between the two has been very rocky. But, I digress.)
So what is Adobe supposed to do about this state of affairs? Keep providing updates for users who CHOOSE to break their installations by installing the latest and greatest OS? Yes, it's a choice to update your OS. And like every choice, you need to do the research before making the decision - particularly when you have been seriously burned by an uninformed choice in the past. Fool me once, shame on you. Fool me twice - well, I'm sure you know the rest.
Like other posters in this discussion, I am still on Win. 10. I have been using computers since DOS 4 was the OS. I know enough not to update right away if I can avoid it. As Chuck said: If it ain't broke . . . . However, if and when I choose to upgrade to Win 11, I know that Microsoft provides utilities to ensure that my existing hardware and software is compatible with the new version before I dive in. And when a Win 10 monthly updates sometimes breaks something, M$FT - the OS developer - usually fixes it within days or provides an easy way to roll back the OS update. It does not expect other software developers to fix its code. Apple apparently has a different business model.
So, while I sympathize with Elements Mac users who find that their earlier version is not working with the latest OS put out by Apple, I am not going to expect Adobe to provide an update on the day the new OS is released. Apple is notorious for releasing software code that is changed at the last minute. What I don't understand is why Mac users think that the problem is Adobe's and not the OS manufacturer who releases a product that won't work with legacy software. And I also don't understand why Adobe should be the one to send notifications to its users that if you use a competitor's product, it will break your current software. That is Apple's responsibility.
And since we have still not been told by any Mac user on this forum exactly what the problem is, we have no way of gauging whether it is a universal problem or only a limited one.
Having said all of that, I will bring this thread to the attention of the Adobe powers-that-be so that there can be further clarification of this issue, if necessary.
... View more