Quote:
Originally posted by franksargent
My reply to the above, in order is, no, yes, no!
A nonsense answer? Read the thread, how many people are pointing the finger of blame at themselves? At Apple?
Nope, you blamed Apple, not I. "Apple is at fault for their update methods."
Is there any consistent pattern to instillation issues posted so far? I don't see one in the FEW posts in this thread so far, but maybe later, who knows. But I doubt that a significant pattern will emerge now or in future OS updates, IMHO updates under 10.4 are pretty seemless, not like the situation in the 10.2 era, these things (OS X instillation procedures) tend to reach mythological proportions over time, people become old school, and just repeat previous procedures, unquestioned.
And that's one of my points, Apple controls the HW/OS chain, while Microsoft does not, yet Apple needs the 12 step AA program to "properly" update the OS, while Microsoft updates are, in a word, seamless. No detach this, permissions that, etcetera! WTF, who wins the ease of use argument here?
"And that means doing what we presented." And what EXACTLY was that explicit stepped procedure, might I ask? Should I listen to HeX cook #1, HeX cook #2, HeX cook #3, ..., ad infinitum. Let's see now 12 steps makes this a 12 factorial problem, 479,001,600 HeX cooks in the kitchen! And what EXACTLY is the "OFFICIAL" word from Apple on installing updates (no Apple support discussion posts please), seeing as I just clicked through all that stuff via Software Update, seeing as I like seamless OS integration on par with Microsoft products? Is that to much to ask of Apple? I think not!
WRT backups, my comment "burn baby burn" was WRT DVD burning as the preferred low cost method of redundancy/storage, and I do this on an almost daily basis. Same goes for (8GB/4GB) flash drives WRT mission critical data, I'm constantly moving data between my home Mac and 2 work PC's.
My reply to the above, in order is, no, yes, no!
A nonsense answer? Read the thread, how many people are pointing the finger of blame at themselves? At Apple?
Nope, you blamed Apple, not I. "Apple is at fault for their update methods."
Is there any consistent pattern to instillation issues posted so far? I don't see one in the FEW posts in this thread so far, but maybe later, who knows. But I doubt that a significant pattern will emerge now or in future OS updates, IMHO updates under 10.4 are pretty seemless, not like the situation in the 10.2 era, these things (OS X instillation procedures) tend to reach mythological proportions over time, people become old school, and just repeat previous procedures, unquestioned.
And that's one of my points, Apple controls the HW/OS chain, while Microsoft does not, yet Apple needs the 12 step AA program to "properly" update the OS, while Microsoft updates are, in a word, seamless. No detach this, permissions that, etcetera! WTF, who wins the ease of use argument here?
"And that means doing what we presented." And what EXACTLY was that explicit stepped procedure, might I ask? Should I listen to HeX cook #1, HeX cook #2, HeX cook #3, ..., ad infinitum. Let's see now 12 steps makes this a 12 factorial problem, 479,001,600 HeX cooks in the kitchen! And what EXACTLY is the "OFFICIAL" word from Apple on installing updates (no Apple support discussion posts please), seeing as I just clicked through all that stuff via Software Update, seeing as I like seamless OS integration on par with Microsoft products? Is that to much to ask of Apple? I think not!
WRT backups, my comment "burn baby burn" was WRT DVD burning as the preferred low cost method of redundancy/storage, and I do this on an almost daily basis. Same goes for (8GB/4GB) flash drives WRT mission critical data, I'm constantly moving data between my home Mac and 2 work PC's.
You're the one not reading this properly.
As I've said, Apple themselves recommends these methods. What more do you need to know?
But, then they pander to the "Oh my-God, I don't understand this, it's too HARD!", crowd, by not requiring it.
What they should do, as I've also said, is to make it part of their update procedures, so that it can't be avoided.
Will this prevent all problems? Of course not! But many "problems" are not actually problems, in the sense of being bugs in the update, other than in the sense that Apple DOES warn people that certain third party software, such as hacks, might cause unexpected problems with the update.
That's also pretty explicit. But, again, Apple goes and does what it does during the update, removing critical parts of that software, without warning, and thereby causing problems.
So, yes, this is Apple's fault.
But, fault also lies with the people who rush out to be the first to download, and install, an update, or upgrade, without waiting to see what problems they might expect from it, and how to avoid it.
But, again, Apple doesn't warn about this either, and the update just appears in Software Update, so people, without thinking, install it.
