re: A great problem indeed #
Posted Tuesday 10th March 2009 23:36 GMT
While I can understand why you think Adobe should have a separate systray app to check for updates, I'm torn on that issue. While I do think software products should have auto-update mechanisms that the user can choose to use (or choose to not use, if the user so desires), I feel that every product having its own updater is an unnecessary drain on system resources.
What software authors should do is agree on a framework by which product updates can be looked for, downloaded, and installed. That way, the user could install a single application which could keep all installed products updated (similar to the way various Linux distributions use one updater app, but instead of updating software packages from the distro's repository, the app would check for and update from each product's home). With that approach, the user would only need one updater app, thereby reducing the resources consumed and allowing much greater control over the updates (frequency of checks, choose whether or not to create a restore point before updating, update method [auto, download+notify, notify-only], etc). But for this to work, software authors would have to agree on a standard update method for checking versions of installed products, checking the product's home for the latest version, how to download the latest version (including any required user authentication), and how to update the software (whether the patch would be an .exe, .msi, or some other format). Preferably, Microsoft could integrate Windows Updates into such an updater so that all updates can be done from one app. It would be much more convenient for the user, and much less confusing to the user.



