2 ms·

But which of these are problems in configuration files written by a human? That is the aim of the format. Moreover in applications were there could be issues, i

But which of these are problems in configuration files written by a human? That is the aim of the format. Moreover in applications were there could be issues, it would most certainly be tied to very specific fields and you would want specific application logic to handle that field. Now if people misuse it as a data exchange format or so, yes I agree with you, but at that point just use a binary format instead.

jiggawatts 6y ago
> That is the aim of the format. That doesn't matter at all. The author's aims will be ignored if this format is used for anything even vaguely important. Eventually it'll need tooling to both read and write it. DevOps pipelines, applications with GUIs, or something will need to both parse and generate this format in a consistent way. There is no such thing as a human-write-only format in widespread use. Even programming languages are regularly generated by tools such as RPC API codegen tools, LINQ-to-SQL and the like.