[147372] in cryptography@c2.net mail archive
Re: [Cryptography] encoding formats should not be committee'ized
daemon@ATHENA.MIT.EDU (James A. Donald)
Mon Sep 30 20:43:54 2013
X-Original-To: cryptography@metzdowd.com
Date: Tue, 01 Oct 2013 10:10:15 +1000
From: "James A. Donald" <jamesd@echeque.com>
To: cryptography@metzdowd.com
In-Reply-To: <2A0EFB9C05D0164E98F19BB0AF3708C711D6DEB338@USMBX1.msg.corp.akamai.com>
Reply-To: jamesd@echeque.com
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
On 2013-10-01 04:22, Salz, Rich wrote:
> designate some big player to do it, and follow suit?
> Okay that data encoding scheme from Google protobufs or Facebook thrift. Done.
We have a complie to generate C code from ASN.1 code
Google has a compiler to generate C code from protobufs source
The ASN.1 compiler is open source. Google's compiler is not.
Further, google is unhappy that too-clever-code gives too-clever
programmers too much power, and has prohibited its employees from ever
doing something like protobufs again.
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
