Skip to content

Instantly share code, notes, and snippets.

View v-braun's full-sized avatar
🏗️
(∩`-´)⊃━☆゚.*・。゚

Viktor Braun v-braun

🏗️
(∩`-´)⊃━☆゚.*・。゚
View GitHub Profile
@czechboy0
czechboy0 / contents.md
Last active March 4, 2016 22:46
We need to talk about JSON "parsers".

We need to talk about JSON "parsers"

For the sake of a vibrant Swift community, we need to call things what they are. And what they aren't.

I recently wrote a JSON parser to accomodate for the lack of NSJSONSerialization on Linux. When searching for an existing one, I was caught by all these libraries which called themselves JSON parsers, but were in fact just wrapping calls to an actual underlying parser (usually NSJSONSerialization). They only provided convenience functions for unwrap values from dictionaries and mapping data to objects.

Those libraries are JSON-to-object mapping libraries. Those are JSON convenience function libraries.