@RobLoach 

We didn't want to replace `cson` or use any of it's code.  I think you were just looking at the wrong repo.

Jan's goal was to implement a very slim, simple cson parsing engine that could be included in any other project that needed safe parsing and wanted to provide features on top of that.  It's sort of like how `request` provides extra features on top of `http` to make it more usable for developers.

Maybe we should have called it `safe-cson-parsing-core` instead.  That might have been a better name.