Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Although according to benchmarks JSONKit is faster, the Github readme is full of warnings that illformed JSON leads to crashes, etc.
For me it is more important that there is no crash, and that an ilformed Unicode JSON or other subtle error in the JSON file does not cause a crash.
Maybe the speed increase comes from it’s strictness and unforgivingness towards errors?
Is NSJSONSerialization more robust in this regard?
This is a somewhat subjective question in that it can only be answered in terms of the experiences of myself and other developers.
I have used both
JSONKitandNSJSONSerializationand greatly prefer the latter. Irrespective of what the benchmarks indicate, I have not noticed a difference in speed in everyday use. However, I am also in the habit of doing my deserialization in a background thread, so the speed differences may not be apparent in the UI.