YAML: Probably not so great after all

Re:YAML: Probably not so great after all by jtdev on Sunday August 18, 2019 @10:56PM (#20734535)

I often hear the “comments aren’t supported” argument against JSON, but as a daily consumer, creator, and maintainer of JSON, I honestly can’t recall ever _really_ needing comments in JSON. It tends to be somewhat self documenting in my experience.

[ Parent | on HN ]

Re:YAML: Probably not so great after all by h1d on Sunday August 18, 2019 @11:05PM (#20734567)

A config file without comments can mean serious annoyance.

If JSON was developed more recently on places like GitHub, it would never have ended up like that with that many deficiencies.

[ Parent | on HN ]

Re:YAML: Probably not so great after all by nine_k on Sunday August 18, 2019 @11:06PM (#20734571)

When maintaining a JSON file, did you ever happen to wonder why a particular value is what it is?

This is where comments belong.

[ Parent | on HN ]

Re:YAML: Probably not so great after all by CriticalCathed on Monday August 19, 2019 @12:10AM (#20734826)

If it's that important and complex, have an accompanying README that lists line numbers and comments.

[ Parent | on HN ]

Re:YAML: Probably not so great after all by js8 on Monday August 19, 2019 @01:59AM (#20735245)

Good idea! And then put a comment into the configuration file that refers to where the documentation is.. ah, f__k!

[ Parent | on HN ]

Re:YAML: Probably not so great after all by meddlepal on Monday August 19, 2019 @12:29AM (#20734905)

Lesson to learn: Nobody reads the docs.

[ Parent | on HN ]

Re:YAML: Probably not so great after all by CriticalCathed on Monday August 19, 2019 @03:14AM (#20735593)

This is such a dumb aphorism. I read and create docs every single day.

If the comments are so critical that it is a problem, then an accompanying file with those comments would be used. Otherwise, it's just a bunch of crocodile tears.

[ Parent | on HN ]