4 ms·
Oh I don't doubt that there are various inefficiencies, but I dispute the characterization that this inefficiency is "wrong". I think it's clear by now that the
by camgunz 3y ago
Oh I don't doubt that there are various inefficiencies, but I dispute the characterization that this inefficiency is "wrong". I think it's clear by now that there's not "1 text format to rule them all", whether we're talking XML, JSON, HTML, SGML, TOML, YAML, JSON, RFC 2822, CSV, or whatever. Depending on your use case, one of these is better than the others. Like I definitely don't want to serialize objects into TOML. I also definitely don't want to deal with JSON for configuration.
> ...but a schema can catch that stuff.
100%; it's amazing to me the number of projects that essentially accept arbitrary structures and/or values here. I think no matter whether you're using YAML/TOML/JSON/etc. you oughta be using something to validate.