3 ms·
The problem is not 'someone is not correctly following the serialization rules', the problem is 'the serialization rules are quite terrible'. This is not some
by sfvisser 6y ago
The problem is not 'someone is not correctly following the serialization rules', the problem is 'the serialization rules are quite terrible'.
This is not some interesting trade-off, this problem is fixable on all axes by using non-ambiguous, non-overloaded typing rules for your config format.
Even JSON and XML got this right.
- bmn__ 6y ago> The problem is not 'someone is not correctly following the serialization rules' Yes, yes, I pointed that out. grep "immediate cause" and "indirect root" > the serialization rules are quite terrible Did that need to be said explicitly? I agree FWIW. I have already made a value judgement mildly against YAML, in case that's not clear. It's only mild because the problem can be worked around. I think this approach is more practical than moving the whole world over to a completely different thing. > problem is fixable […] non-ambiguous […] rules Is the implication here that you say YAML is ambiguous? It's not. I don't want sloppy analysis. To be precise, the ambiguity is imagined, it does not exist on the spec or software level, only in the head of people.