News for hackers. Stuff that matters.
Re:Libvirt – The Unsung Hero of Cloud Computing (2013) by throwaway189262 on Friday September 04, 2020 @01:28AM (#24371975)
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.

Re:Libvirt – The Unsung Hero of Cloud Computing (2013) by _-___________-_ on Friday September 04, 2020 @03:49AM (#24372713)
Ugh, please name and shame the [de]serializer that was silently converting a string to a boolean.
Re:Libvirt – The Unsung Hero of Cloud Computing (2013) by bonzini on Friday September 04, 2020 @07:19AM (#24373927)
Not sure about JSON, but YAML has the Norway problem: https://hitchdev.com/strictyaml/why/implicit-typing-removed/
Re:Libvirt – The Unsung Hero of Cloud Computing (2013) by formerly_proven on Friday September 04, 2020 @09:43AM (#24374829)
JSON does not, because JSON is explicitly typed:

   - "... - string
   - 14, 14.5 - number (problematic)
   - false, true - bool
   - {... - object
   - [... - array
   - null
No cute abbreviations.
Re:Libvirt – The Unsung Hero of Cloud Computing (2013) by throwaway189262 on Friday September 04, 2020 @04:22AM (#24372889)
The problem we ran into is that they can all be configured to do whatever. There's no consistently or standard
Re:Libvirt – The Unsung Hero of Cloud Computing (2013) by _-___________-_ on Friday September 04, 2020 @11:08PM (#24381100)
well, there's the JSON standard, which does not define "false" and false as equivalent.
Re:Libvirt – The Unsung Hero of Cloud Computing (2013) by danmur on Friday September 04, 2020 @07:17AM (#24373918)
Not a big fan of JSON myself but that sounds more like a bad implementation than ambiguity in the spec.