3 ms·

> It's just that seems to be stuck in 2001, while others finally managed to sort their crap out. Those others do not include Apple as anyone who's been indefin

> It's just that seems to be stuck in 2001, while others finally managed to sort their crap out. Those others do not include Apple as anyone who's been indefinitely waiting for "installing" OSX updates can confirm - and the OSX fixes needed have the same weird incantation like qualities as the fixes for Windows updates (i.e. remove update, then restart, then run again, then panic, redo-sequence). No particular hate meant for Apple or MS.. but seriously, learn how to write a basic update mechanism that do not include random-fail-over.

givinguflac 11y ago
I've managed a ton of Macs and can't say I've ever come across the need to remove an update, or really any issue with updates failing, but maybe I'm lucky?
revscat 11y ago
I manage Macs for myself and my family, as well having used many through my employer over the years. I have never seen what you describe.
headShrinker 11y ago
I manage Windows and Mac networks. Mac updates may take up to 5 minutes to discover necessary updates, resulting in 5 - 10 package downloads, even on machines that haven't been regularly updated. Windows, depending on the version can take upwards of 20 - 30 minutes, with up to 50-60 package downloads, and on machines that haven't been updated recently, 1 - 2 hours, and hundreds of package retrievals. > OS X fixes needed have the same weird incantation like qualities as the fixes for Windows updates I find your statement inaccurate. Even if the update operations are fairly similar in Windows and OS X, the latter's update system seems fairly efficient. OS X doesn't have the libraries and dependences hell that windows does. The update model fits well in to the OS X environment, not well at all in Windows. Also, Mac updates that update system files are 'rare' and usually only require one reboot. Windows often requires 2 or 3 reboots. Again, I believe this is because of the dependancies and libraries Windows is forced to maintain and keep up to date. Mac's don't hang on update or install, frankly, Ever, unless there is something very wrong.
- maaaats 11y ago
  The update procedure works fine, the newly updated OS X seldom so. Far too often updating OS X means having something break.

givinguflac 11y ago

I've managed a ton of Macs and can't say I've ever come across the need to remove an update, or really any issue with updates failing, but maybe I'm lucky?

revscat 11y ago

I manage Macs for myself and my family, as well having used many through my employer over the years. I have never seen what you describe.

headShrinker 11y ago

I manage Windows and Mac networks. Mac updates may take up to 5 minutes to discover necessary updates, resulting in 5 - 10 package downloads, even on machines that haven't been regularly updated. Windows, depending on the version can take upwards of 20 - 30 minutes, with up to 50-60 package downloads, and on machines that haven't been updated recently, 1 - 2 hours, and hundreds of package retrievals. > OS X fixes needed have the same weird incantation like qualities as the fixes for Windows updates I find your statement inaccurate. Even if the update operations are fairly similar in Windows and OS X, the latter's update system seems fairly efficient. OS X doesn't have the libraries and dependences hell that windows does. The update model fits well in to the OS X environment, not well at all in Windows. Also, Mac updates that update system files are 'rare' and usually only require one reboot. Windows often requires 2 or 3 reboots. Again, I believe this is because of the dependancies and libraries Windows is forced to maintain and keep up to date. Mac's don't hang on update or install, frankly, Ever, unless there is something very wrong.

maaaats 11y ago
The update procedure works fine, the newly updated OS X seldom so. Far too often updating OS X means having something break.