> If you want better interchange you should be pushing it to be included along b64 at the language level not trying to get every dev to include extra dependenci

> If you want better interchange you should be pushing it to be included along b64 at the language level not trying to get every dev to include extra dependencies at either side of the exchange. Oh, absolutely. JavaScript Object Notation became a defacto standard purely because js could parse it natively. Then `json` was adopted as part of the standard python libraries, within PHP, etc... Once upon a time, even stuff like base64 encoding/decoding required someone to write the code for it. Agreed, it requires pushing to get useful stuff into "batteries included" stdlibs. We're using JavaScript Object Notation because.... Isn't the name quite telling? :-)