The only thing that really annoys me about JSON is that it doesn’t allow comments.
Comment on What is the best file format for configuration file?
AverageCakeSlice@sh.itjust.works 1 year ago
JSON by a mile. I hate the YAML plague, it’s some of the most unintuitive syntax I’ve seen and yet it’s everywhere in DevOps/SysOps.
nightmareofahorse@programming.dev 1 year ago
GitHub Actions and Azure DevOps had me hating on YAML pretty quickly
kersplort@programming.dev 1 year ago
YAML works better with git than JSON, but so much config work is copy and pasting and YAML is horrible at that.
Having something where changing one line doesn’t turn into changing three lines, but you could also copy it off a website would be great.
Hexarei@programming.dev 1 year ago
Yeah, any language in which whitespace count is semantically significant can go suck fat nards.
derpgon@programming.dev 1 year ago
I mean, a valid JSON is a valid YAML
Hexarei@programming.dev 1 year ago
I hate that you’re correct lmao
bignavy@programming.dev 1 year ago
Not sure whether fantastic troll or just no exposure to Python.
Either way…I’m here for it.
Hexarei@programming.dev 1 year ago
Neither, I’ve written plenty of Python and I know how useful it can be. However, as someone who is neurospicy, I find languages that have semantically l significant white space to be frustrating to read.
Sure, there are tools to help with it. Sure, they help. But they don’t replace how much more useful curly braces are at defining scope.
bignavy@programming.dev 1 year ago
You’re not wrong. Having to figure out which element is borked in a yaml file is not great. And the implementation using yaml is all over the place, so even though tools do exist, they’re mediocre at best.
But, to be fair, Python has always done the same to me. As a fellow Neuro-spicy (and with a background in Java and C# and JavaScript), although the tools are better to point you in the right direction, significant white space (or indentations) are significant white space (or indentations).🤷♂️