Re: Reg: PyYAML grammar
Paul Lambert <[email protected]>
| Newsgroups | gmane.text.yaml.general |
|---|---|
| Message-ID | <[email protected]> |
Ok - the YAML community and binary encoding do not appear to be compatible. Too bad your world view is so limited. Take a look a protobuf as an example of combining human readable and binary encodings if you want to see a worked hybrid. The notion I was presenting was not that binary was the primary representation - but that the human readable and a binary encoding could coexist. Note that I'mm working with vendors building consumer devices, sensors, wireless protocols .. so the efficiency is quite important ... and zip is not a viable option. Paul > -----Original Message----- > From: Steve Schafer [mailto:steve-bHQK/pGi2DVWk0Htik3J/[email protected]] > Sent: Monday, June 13, 2011 12:40 PM > To: Paul Lambert > Cc: [email protected] > Subject: Re: [Yaml-core] Reg: PyYAML grammar > > On Mon, 13 Jun 2011 11:45:54 -0700, you wrote: > > > x0506123456789AB (total length 8 bytes) > > This is precisely the kind of thing that YAML was designed to > eliminate! > Look at the top-priority goal of the YAML standard: "YAML is easily > readable by humans." Readability trumps _everything_. > > Bits are cheap. Unless you have a truly compelling reason to worry > about > the size of your data (e.g., you're working with an embedded CPU that > has only a few kB of RAM), forget about this kind of compression. It > will only come back to bite you in the butt later. > > And if you really do have a reason to worry about the size of your > data, > you probably shouldn't be using YAML. > > -Steve Schafer ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev