4 ms·
IMHO the arguments in your link aren't particularly convincing. The three main points seem to be verbosity (defined in terms of total number of characters for a
by saghm 6y ago
IMHO the arguments in your link aren't particularly convincing. The three main points seem to be verbosity (defined in terms of total number of characters for a given file, which is not nearly as important to me as readability), not having indentation be significant (which might be downside to a Python programmer but feels like a win to me), and having explicit syntax to distinguish between types (e.g. strings being quoted, which is preferable to me, since it makes them stand out as values compared to the keys). If these are the strongest arguments against TOML, I find myself fairly convinced that TOML is probably the format I'd like to use most even though I was I different towards it before clicking the link.
- throwaway894345 6y agoI would be very interested in an experiment in which participants are required to write Kubernetes manifests in YAML or TOML, and what the analysis suggests they prefer (after controlling for the right set of variables). I don’t like YAML, but TOML stops being nice very quickly as the size or complexity of the data increases IMO.
- afiori 6y agoThe second point is not about whitespace, but rather about how you can write your document out of order. specifically TOML supports a syntax that allows to write documents like: (not actual syntax) a.b=1 a.c=2 d=3 a.e =4 that would translate to {a:{b:1,c:2,e:4},d:3}. So the criticism is that (in various cases) you need to read the entire document to be sure to have fully parsed one subtree of the document.