4 ms·

If it can be done in JSON it can also be done in YAML. I pick YAML.

• crooked-v 10y ago
  If the idea is to reduce verbosity, I'd much prefer CSON. YAML just has way too much "magic" parsing behavior.
  • Entangled 10y ago
    Not bad, a second close just behind YAML in my picks. Nothing can beat this: name: Taylor Swift Absolutely nothing, no matter how you dress it.
    • mst 10y ago
      I prefer name "Taylor Swift" which is how JSONY works (which was an experiment ingy and I put together)
    • allover 10y ago
      Right, but the problem is YAML parsers are crazy hard to implement correctly/safely. Its spec is an order-of-magnitude more complex than JSON.
• seagreen 10y ago
  Have you read the specs for both? You should read the JSON spec. It will take you ten minutes. The YAML spec (http://yaml.org/spec/1.2/spec.html http://yaml.org/spec/1.2/spec.html) may take you a little longer. . .
  • Entangled 10y ago
    S-expressions will take you ten seconds still nobody uses them. YAML is made to simplify the lives of the reader and the writer, not the parser. Let the parser suffer, let the coder rejoice. You pick your own level of suffering, I pick mine. Deal?
    • cocktailpeanuts 10y ago
      What language you use doesn't really matter much when you can easily transform one into another. I think that's exactly the case with JSON and YAML.