Well put Koen.

The other thing that's interesting is that with the build chain being piqi
-> proto files, you can add support for languages to automatically support
your data schema other than what the original protocol buffers project
provides for. So, originally pb started with python, java, and C/++. Now it
supports Google's go and all kinds of other languages.

On Thu, Feb 26, 2015 at 10:07 AM, Koen De Keyser <koen.dekeyser@gmail.com>
wrote:

> I've worked with Piqi, converting a project that was using custom
> serialization to Protobuf. This was a fairly pleasant experience: the main
> developer was very responsive and the code base for the code generator is
> sufficiently clean that it made adding custom functionality quite easy.
>
> The main reason I went with Piqi is the code generation functionality: one
> of the main reasons to adopt something like Protobuf is the possibility of
> generating code in a multitude of languages (e.g. Python for scripting /
> testing purposes) from a single definition file (the proto file in this
> case). Any change there is automatically picked up by the build process in
> all of the languages, so your code stays in sync across languages. This is
> not the case if the definition of the struct is in Ocaml itself.
>
> Koen De Keyser
>
> On Wed, Feb 25, 2015 at 5:58 PM, Trevor Smith <
> trevorsummerssmith@gmail.com> wrote:
>
>> Hello,
>>
>> Is anyone out there using OCaml with Protobufs? If so, what library/tools
>> are you using, and how do you like the setup? Also, are you using Protobufs
>> in a production setting?
>>
>> I found online but have not used any of the below myself:
>>
>> 1) piqi - http://piqi.org/
>> 2) obitz - https://github.com/orbitz/ocaml-protobuf
>> 3) whitequark's protobufs - https://github.com/orbitz/ocaml-protobuf
>>
>> Curious to hear your experiences. Thank you.
>>
>> Trevor
>>
>
>