Chambers wrote:
> To me, one of the most important things a piece of code (whether it's an 
> entire program, or just a single routine) can do is fail gracefully.  If 
> it fails, enough context and information should be given that you know 
> why it failed.
> 
> iTunes is absolutely horrible at this.  Apparently, Apple thinks that 
> "failing gracefully" means quietly ignore the error with no record of it 
> being kept anywhere.  In other words, you don't even *know* there's an 
> error.  Your only clue is that the expected result didn't actually 
> occur.  Once you figure out there's been an error, you have no idea what 
> caused it.
> 
> Talk about bad practice.

For the average iTunes user (think:  grossly ignorant teenager), 
feedback would be useless.

Regards,
John

Post a reply to this message