Quote:
Originally Posted by
JeffDM 
I'm sure there are other unsaid reasons, but this reason does have some validity too.
Please explain why Apple should be expected to make an update notification system for a company that failed to make their own? Adobe is a grown-up company, expecting Apple to dote on Adobe like an overgrown infant like that has to be an insult against Adobe.
I would say the reason why it's a problem now and not back in 2003 or whenever is Flash didn't have known critical security bugs until somewhat recently.
I don't think it has any validity whatsoever. Adobe has always had an update mechanism for Flash. The non-profit Mozilla.org has always used this mechanism for Firefox. In fact, Firefox checks all plug-ins for being up to date. Other browsers besides Safari have done this from the beginning as well.
The problem is that there's no way for a plug-in by itself to take control of the OS and check for an update and install. That's the constraint on plug-ins that Apple placed in Safari. A plug-in can be checked for being up to date by either pinging the server through Software Update or having the browser visit a page that runs a script checking the version number that's installed. It's very simple code and low impact. It makes far more sense for SU or Safari to do this than having every plug-in developer create their own update mechanisms, not that they could with Safari.
In short, Adobe provided the update mechanism on their end, and other browser developers from the beginning implemented this, except for Apple.
And now, Apple isn't doing anything to improve security, which is why I'm saying there's no validity to this. What Apple is doing is making sure people get the right version of Flash when they install, but then doing nothing to check to make sure they keep up to date. How is that more secure than all the other browsers that do check to see if they're up to date?
While Flash may have had an increase in security bugs recently, it's always had a variety of other issues that were fixed with updates. Most often these updates occurred with new versions of Safari being installed or web developers doing the version check, but the version frequency has actually tapered off since 2003.
But again, if this was about security, Apple could very easily implement update checking for Flash, (and other plug-ins), and the bottom line is that mechanism would offer the best security for Mac users as well as the best user experience.
Even if Apple was to have the courage to say, "We just hate Flash and will do anything to destroy it", that would be perfectly fine...no complaint from me, but if Apple wants to improve security, they still should do update checking.
And remember, this comes from someone who hates Flash and wants to see it die. However, since it's still out there and being used, Apple should look at what's in the best interest of its users as opposed to battling over this, and not being honest about their actions.