3 ms·
Haha yeah JSON is a terrible config format. As another poster mentioned, no comments. But the other big problem is inconsistent serialization. Null vs missing p
by throwaway189262 6y ago
Haha yeah JSON is a terrible config format. As another poster mentioned, no comments. But the other big problem is inconsistent serialization. Null vs missing props, conversion of "true" to true. I've lost track of the number of times I've had to workaround differences in the serializer vs deserializer on other end.
It's really quite bad format for how ubiquitous it's become.
- _-___________-_ 6y agoUgh, please name and shame the [de]serializer that was silently converting a string to a boolean.
- throwaway189262 6y agoThe problem we ran into is that they can all be configured to do whatever. There's no consistently or standard
- _-___________-_ 6y agowell, there's the JSON standard, which does not define "false" and false as equivalent.
- bonzini 6y agoNot sure about JSON, but YAML has the Norway problem: https://hitchdev.com/strictyaml/why/implicit-typing-removed/ https://hitchdev.com/strictyaml/why/implicit-typing-removed/
- formerly_proven 6y agoJSON does not, because JSON is explicitly typed: - "... - string - 14, 14.5 - number (problematic) - false, true - bool - {... - object - [... - array - null No cute abbreviations.
- danmur 6y agoNot a big fan of JSON myself but that sounds more like a bad implementation than ambiguity in the spec.