{"action":"opened","issue":{"number":79,"created_at":"2011-10-18T23:42:21Z","pull_request":{"diff_url":null,"patch_url":null,"html_url":null},"body":"The ifdefs for how JSON is handled currently attempt to loosely fallback to JSONKIt. This is unsafe and not very well thought out. The user of the library should really be explicit if wants to add the extra JSONKit dependency or just use Foundation JSON and they should use only one library instead of trying to fallback. \r\n\r\nThe reason is that the two are not perfectly compatible in what they return. Both have subtle differences that can turn into weird bugs for the developer getting something they didn't expect. On top of that, JSONKit is dramatically faster so doing it as fallback after Foundation JSON seems silly. \r\n\r\nI think that instead of requiring JSONKit in both situations, allow the user to choose if he wants to add an extra dependency or not to his project. I'm perfectly happy with the built in slower Foundation's JSON support only to reduce my app size and not have to configure another set of files not to build with ARC in my project.  \r\n","comments":0,"title":"Foundation JSON handling is silly. (Pull request)","updated_at":"2011-10-18T23:42:21Z","url":"https://api.github.com/repos/gowalla/AFNetworking/issues/79","id":1984542,"assignee":null,"milestone":null,"closed_at":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/ba78b57d00a1ed5c2dd21c1feba778d6?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"ba78b57d00a1ed5c2dd21c1feba778d6","url":"https://api.github.com/users/zbowling","id":245886,"login":"zbowling"},"html_url":"https://github.com/gowalla/AFNetworking/issues/79","labels":[],"state":"open"},"legacy":{"number":79,"action":"opened","issue":1984542}}