Jonathan Wight

@schwa Ah God.

@drance @schwa Wait, it’s the mixing/matching that’s a problem, right? Subclassing NSError isn’t a "Nooooooooo".

@danielpunkass @drance my main dislike is that it’s it’s absolutely purely redundant. It’s like subclassing NSString…

@schwa @danielpunkass @drance I get where they're coming from. NSErrorDomain always seemed unnecessary when you could just subclass instead.

@dmdeller @danielpunkass @drance no.

@schwa @danielpunkass @drance OK.

@dmdeller @danielpunkass @drance seriously though, like I said before it’s like subclassing NSString. You need a damn good reason,

@schwa @drance noob question but why is sub classing NSError bad?

@saurabhg @drance Can you think of a good reason to subclass?

@schwa @drance never felt the need but from docs ‘Apps may subclass to provide better localized errors by overriding localizedDescription.'