>do you really want to implement your own json parser? On the recreational and creative side, maybe, but not as much as coming with an original exchange format

>do you really want to implement your own json parser? On the recreational and creative side, maybe, but not as much as coming with an original exchange format which is a better feat to the specific case at hand. On a professional side, if JSON support is a burden engraved in the specification so be it. Then having the transformation of the PL native data structure back and forth to various other formats shipped in the standard library is really the best that can hoped. As second best case it is having a single clearly preponderant and well maintained library. Otherwise, bet among a plethora of possible libraries is becoming less attractive compared to building something internally brewed.