4 ms·
Honestly, even as a transport datatype it's always bothered me that JSON lacks a well defined number. I mean, if your going to allow infinitely large numbers sh
by nixpulvis 8y ago
Honestly, even as a transport datatype it's always bothered me that JSON lacks a well defined number. I mean, if your going to allow infinitely large numbers shouldn't you explicitly support them with Big types?
EDIT: and if you want fixed size numbers (for many good reasons) then what size?
JSON as a config is another story, and I completely agree with this link. I'm a personal fan of TOML[1] for many purposes.
[1]: https://github.com/toml-lang/toml https://github.com/toml-lang/toml
- mcculley 8y agoJSON is fine as a transport datatype between two bits of code you completely control (e.g., webapp front end and back end). It is a terrible choice as soon as you want to publish and document a public protocol.