On Jul 30, 2010, at 10:18, Brian Postow wrote: > I've been following this list for a while, and have seen very few questions > about the IK family, even though I've had a series of problems with it. Is it > known that it is a lousy way to do things? or am I the only one who has these > problems?
I don't think you're the only one who's had problems, but I think you may have persisted longer in the face of problems than anyone else. (I only lasted a day and a half with it, before I took my code, burned it, and buried it with plenty of garlic at a nearby crossroads.) From my limited experience with IK, I'd say its main problem is its inscrutability. It general purpose is clear, but there isn't much information about what it's supposed to do in any given situation, whether it has any given behavior, and how to get the behaviors it has to operate. Possibly it's extremely buggy, but it's too inscrutable to determine whether specific cases are (a) bugs, (b) you're Doing It Wrong™, or (c) it Doesn't Do That™. It seems to me IK is one of a handful of frameworks that suffers from gross design-by-implementation. That is, what it's supposed to do is defined by what it actually does, which is not much help to the developer. Unlike with most frameworks, the API isn't really a contract with the developer, but more a series of "Push Here For A Chance To Win" buttons. FWIW. _______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [email protected]
