> Does the likely over a dozen point difference in our comment scores on your our posts here not give you any indication that this just might not be an isolated

> Does the likely over a dozen point difference in our comment scores on your our posts here not give you any indication that this just might not be an isolated issue? I can't see the point difference between our comments, how would I know that? Moreover, why should I care? Congrats, you've proven other techs also don't like things that confuse them and would prefer to join in your bitching. > Or are you one of these people that is never wrong and can't admit that you might not have experienced every possible use case or code path of iTunes? You're acting like I'm saying iTunes is perfect. It's not, it's riddled with issues and a frank conversation on it's future is important. I'm just saying the issues most techs present to me, including the one you did, are the simplest issues to solve and indicative of a weird attitude techs have towards iTunes, where they assume it will fuck them over before trying anything to solve the problem. If you had presented a real issue, I wouldn't have even continued. You instead presented the simplest one that only happens to novice users, so I laid into you appropriately. > Seriously, do you understand the absurdity of what you're claiming, outside of this application or your or I's anecdotes... that the claim that the software is bug free or works perfectly for everyone is just an outlandishly stupid thing to claim as an absolute? That is a ridiculous claim. Good thing I never once said that. > but it's cute that you continue to make absurd assumptions and personal attacks. My point was that any software on a machine with sufficient issues can crash. That wasn't an "absurd assumption or personal attack" it was verifiable truth.