@Another User said:
permissions corruption: we are agree don that point - it ... but is this not nit picking?
an example why i can't consider such issues not as *nit picking*: if you try to extract an archive (eg. the compressed EXS samples from a pro edition DVD) with UnRarX on a machine with corrupt file permissions you get messages like file not found, format error, unexpected quit, sometimes actually nothing. this comes up without having the corruption related to the files from UnRarX or the DVD of course and disappears as soon as you repair permission.
you don't want to know how many hours, days, weeks of user support such a tiny issue can generate ... and of course no one blames OSX, everyone is furious about the *poor behaviour of VSL libraries* - too bad they have that size.
just check out the ratio of support requests for XP and OSX to understand why i'm alittle bit *picky* about fulfilling basic requirements for an OS. unfortunately this is backed up by a marketing campaign which tries to present OSX as the ever and world's best, unfailing, easy-to-use OS when it is not.
i understand and am aware why: because it's a modern multiple purpose and highly complex system - and it would be no shame to admit this instead of reiterating to communicate one would not need to know anything about computers to use them. this is, especially for *NIX, not true.
my example supporting this point of view: how many OSX users know that program code for running processes stays in the memory even if the respective file has been updated - and is it noticeably mentioned somewhere? it is not. the results can be disastrous.
now one can ask either for the technical understanding or instruct to reboot the computer before and after updating something - both contradicts the original and still published apple philosophy leaving us with the decision to choose the less worse ...
christian