News for hackers. Stuff that matters.
Re:JSON5 is a proposed extension to JSON by harshreality on Sunday March 02, 2014 @03:31AM (#7328296)
> As Stormbrew already pointed out, we already have a format that is ideal for configurations (and sure, data exchange, why not), and it is called yaml.

Unfortunately YAML for untrusted input and data exchange is unsafe by default, depending on the language and implementation. A flag might need to be set, or extra modules included like SafeYAML[1] to keep Yaml from instantiating arbitrary objects.

[1] https://github.com/dtao/safe_yaml

Re:JSON5 is a proposed extension to JSON by rat87 on Sunday March 02, 2014 @04:16AM (#7328407)
I thought the problem wasn't with yaml but with allowing deserialize arbitrary objects which is unsafe by default for a format used both for 'trusted' and 'untrusted' input, If you have a json library which tries to allow deserializing arbitrary objects by default (with a load rather then unsafe_load method). Python's pickle serialization is unsafe but it warns you that its unsafe and is not widely used leading to it not being used as a serialization format for for unsafe input.
Re:JSON5 is a proposed extension to JSON by crdoconnor on Sunday March 02, 2014 @03:42AM (#7328328)
>The problem with YAML is it's not safe by default

Why would that be an issue when using it as a configuration format?

Re:JSON5 is a proposed extension to JSON by coldtea on Sunday March 02, 2014 @07:59AM (#7328986)
Because the parsers for that configuration format are unsafe too? Duh!