4 ms·

YAML sounds like the, olde time "hardy hard har" solution to modern extensible languages. Where pretty much "anything goes" to the point of conceiving full blow

YAML sounds like the, olde time "hardy hard har" solution to modern extensible languages. Where pretty much "anything goes" to the point of conceiving full blown tumor executables. People can say what they want about JSON but anything beats the old world of rolling your own serializers and convincing your boss over the hours you've spent reinterpreting some "sporadic flavor" like YAML.

emptyparadise 6y ago
I love JSON, but it sure would be nice to hop into a time machine and force Douglas Crockford at gunpoint to add comments to the spec.
- mastrsushi 6y ago
  Should serialized data allow comments though? I feel that's considered Metadata that could be connoatated elsewhere.
  - emptyparadise 6y ago
    Ideally no, but with JSON being used as a configuration file format and being written by humans, I don't think we have much of a choice.
    - whizzter 6y ago
      Many JSON parsers has flags to enable comment parsing (and someone went ahead and made a "standard" called JWCC that seems to be more or less what these parsers accept) I think that is a good tradeoff, JSON being strict for data interop with the possibility of enabling comments for those cases where people use it for configuration (and specifying it as JWCC)
  - marcosdumay 6y ago
    > Should serialized data allow comments though? Hum... Why not? Serialized data can be written and read by humans too. Besides, if comments are out of scope, there is no reason for them to be textual either.
- reificator 6y ago
  > force Douglas Crockford at gunpoint to add comments to the spec. You mean re-add them. > I removed comments from JSON because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability.
  - emptyparadise 6y ago
    Well the good news is that I found a better use for the gun I brought back to the past to threaten Douglas Crockford.

emptyparadise 6y ago

I love JSON, but it sure would be nice to hop into a time machine and force Douglas Crockford at gunpoint to add comments to the spec.

mastrsushi 6y ago
Should serialized data allow comments though? I feel that's considered Metadata that could be connoatated elsewhere.
- emptyparadise 6y ago
  Ideally no, but with JSON being used as a configuration file format and being written by humans, I don't think we have much of a choice.
  - whizzter 6y ago
    Many JSON parsers has flags to enable comment parsing (and someone went ahead and made a "standard" called JWCC that seems to be more or less what these parsers accept) I think that is a good tradeoff, JSON being strict for data interop with the possibility of enabling comments for those cases where people use it for configuration (and specifying it as JWCC)
- marcosdumay 6y ago
  > Should serialized data allow comments though? Hum... Why not? Serialized data can be written and read by humans too. Besides, if comments are out of scope, there is no reason for them to be textual either.
reificator 6y ago
> force Douglas Crockford at gunpoint to add comments to the spec. You mean re-add them. > I removed comments from JSON because I saw people were using them to hold parsing directives, a practice which would have destroyed interoperability.
- emptyparadise 6y ago
  Well the good news is that I found a better use for the gun I brought back to the past to threaten Douglas Crockford.