On Mon, Jun 13, 2011 at 10:39 PM, Steve Schafer <email@example.com>
On Mon, 13 Jun 2011 11:45:54 -0700, you wrote:This is precisely the kind of thing that YAML was designed to eliminate!
> x0506123456789AB (total length 8 bytes)
Look at the top-priority goal of the YAML standard: "YAML is easily
readable by humans." Readability trumps _everything_.
Yup. This doesn't prevent people from defining all sort of strange binary formats, (which aren't YAML!)... In the example Paul gave, it seems like zip would efficiently encode what he called "tags" (actually, they are simply mapping keys). Well, at least if they are repeated more than once... Reducing the size of Mac addresses and so on would be less effective, but I still think that a simple zip (possibly combined with using a flow style) would make the vanilla YAML file "reasonably" competitive, size-wise, compared to a specially designed binary file format. By "reasonably" competitive I mean "less than twice as big" which, in this day and age, seems "good enough".