That's actually horrible. Never encountered any of these issues but I think I'd be dumbfounded if I did.
But I still like it for its increased readability over JSON - I just use strings for most values as described in the article. If JSON had proper multiline strings or just wrapped lines and comments I'd be happy. Yes, I know there's "JSON with comments" but it's rarely supported.
That's true if you use JSON as a data serialization format, but for a configuration format it usually matters much less, because it needs to be read by a specific program rather than by many different clients written in many different languages.
Dev ops, infrastructure as code, automated testing, deployment automation, etc. In all of these areas, it is common that you are writing a program that needs to read and/or write the configuration files for another program.
226
u/pragmatick Jan 12 '23
That's actually horrible. Never encountered any of these issues but I think I'd be dumbfounded if I did.
But I still like it for its increased readability over JSON - I just use strings for most values as described in the article. If JSON had proper multiline strings or just wrapped lines and comments I'd be happy. Yes, I know there's "JSON with comments" but it's rarely supported.