I find it hard to take these sorts of rants seriously. It's a user who wants to do things their own way, but not bother learning how exactly that is done. I cal

I find it hard to take these sorts of rants seriously. It's a user who wants to do things their own way, but not bother learning how exactly that is done. I call this mixed-level behaviour - e.g. users who won't use the built-in functionality, but not understand or correctly use the alternative more technical methods. Take the mail example, Mail.app already lets him export his mail box, delete his mail etc. He never needed to rifle through ~/Library to get at it. However if he's tech savvy enough to want to do it the manual way, then he should know how to fire up the terminal to access ~/Library, or more simply by holding the option key and choosing "Library" from the go menu. I don't this is breaking osx. While I can't vouch for why he has a magnitude of locked files, given the mail example I have a fair idea of how he's gotten in that situation. While os x does give him the option to gloss past certain locked files. He's likely seeing the error because he's removed files which are "spoken for" (i.e in use), these are often located in ~/Library and it's kind of the point of why ~/Library is hidden. Again, if he wants to be tech-savvy, he should just rm the files, or rm the contents of the trash folder. (Or if it was mail.app responsible, just originally remove the mail from inside Mail.app) OSX certainly has some way to go in addressing this kind of mixed level behaviour, but it's not going to stop you from shooting yourself in the foot. About the other features: while I don't appreciate the iOS-ificiation of mac os, it's trivial to turn these learning-curve reducing features off, and on laptops I find they make more sense than they do when using a mouse + keyboard.