.yaml, .toml, etc?
The one with a validator provided to the user.
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.
Yeah, any language in which whitespace count is semantically significant can go suck fat nards.
Not sure whether fantastic troll or just no exposure to Python.
Either way…I’m here for it.
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.
The only thing that really annoys me about JSON is that it doesn’t allow comments.
Tyson is nice - esp. if you are already using TS/JS.
.xml
XML would be great if it wasn’t for the extended XML universe of namespaces and imports.
XML to transform XML to import into more XML? Can’t we just have a config file that isn’t setting up some big tie in?
It really depends. I usually prefer json. It’s easily understandable from humans and from machines, it doesn’t depends on indentation and above everything else I like it very much 🤣
