Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fast JSON parser for iOS

blog.nextive.com

Post reply on HN
Print view View original

11–15 of 15 posts

Re: Fast JSON parser for iOS

#11

Post by Zev »

schrototo wrote: post #7

Somewhat off-topic, but looking at the readme of JSONKit [1] I found: "At this time, there are no plans to support ARC in JSONKit. Although tenative [sic], it is extremely unlikely that ARC will ever be supported, for many of the same reasons that Mac OS X Garbage Collection is not supported." Which seems kind of weird, seeing as ARC is going to be the default pretty soon. [1] https://github.com/johnezang/JSONKit

Have you ever looked at the code in JSONKit? It makes perfect sense that it won't support ARC. JSONKit has a lot of small optimizations that deal with allocating memory that interfere with ARC and the assumptions the compiler needs to be able to make for ARC to work.

Re: Fast JSON parser for iOS

#12

Post by jmah »

schrototo wrote: post #7

Somewhat off-topic, but looking at the readme of JSONKit [1] I found: "At this time, there are no plans to support ARC in JSONKit. Although tenative [sic], it is extremely unlikely that ARC will ever be supported, for many of the same reasons that Mac OS X Garbage Collection is not supported." Which seems kind of weird, seeing as ARC is going to be the default pretty soon. [1] https://github.com/johnezang/JSONKit

Not that this matters, though, because ARC and non-ARC code can call each other.

Re: Fast JSON parser for iOS

#13

Post by phil »

It's not even plausible. Native binary plist reading is typically about 2x as fast as JSONKit (in my informal benchmarks).

So they claim to be about an order of magnitude faster than binary plists, which would be astonishing if it were true.

Re: Fast JSON parser for iOS

#14

Post by haberman »

haberman's rule for publishing benchmarks: you don't get to claim that you're >2x faster than your already-highly-optimized competitor without explaining why. If you don't know why, you need to figure out why. Without explaining why, I will assume that it's not an apples-to-apples comparison, or that you made a mistake in your benchmarking.
Post reply on HN