Quote:
Originally Posted by eschwartz
In this case, it wasn't a corrupted download (and it would get verified first  ) or people interrupting things in the middle. It was a badly coded update that bricked enough iDevices to receive a fair amount of notice. IOW, yes, Apple did something wrong. I am not sure why you seem to think it is user error, for not backing up their device. FWIW, I agree that backups are crucial, but I don't think my extra habit should exempt developers from the need to avoid pushing broken software.
Also, I was responding to your statement:
I don't, that was never my point, and please stop putting really random words in my mouth.
I am beginning to suspect you are an Apple fanboi  you seem to be excusing anything Apple does as "If you expect 100% perfect [...] you really need to get use to being disappointed". |
Well, if they don't connect to a computer and don't use iCloud, then the only other choice is magic. I could care less what you imagine or suspect. I'll ding Apple when they do things I think they need dinging over. I'm not going to ding Apple because someone failed to back up their device. That's purely a user error.
I'm also not going to ding Apple for failure to achieve 100% perfection, which is what you seem to expect. If someone pushes code which works fine for the vast majority of users, then the odds are it's not broken software. Seriously, how many people had their iPhones brinked out of the some 650 million that are out there? Most of the reports that I've seen seem to point to network issues during the download and it seems to be a small handful. Certainly not enough to trigger reports of wide spread issues, which would indicate broken software.