caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Maxime Ransan <maxime.ransan@gmail.com>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>
Cc: "Louis Roché" <mail@louisroche.net>,
	picflo_2@web.de, "caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] Protobuf for ocaml
Date: Sun, 11 Feb 2018 02:15:12 +0000	[thread overview]
Message-ID: <CAGOKm=S9Mb--zV0_qA9zKN1Oy=-eotGoQx6+Rd+n77yDM=Nv6A@mail.gmail.com> (raw)
In-Reply-To: <CAK7rcp_R_pxUbTw4jYGSoDq7fDdb7wUosw0ZpuhvdO4V66wRXg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]

The difference between ppx_deriving_protobuf and ocaml-protoc is that the
former generates a protobuf schema from an OCaml type while the later
generates the OCaml type from a protobuf schema. They are both using the
same runtime library for the binary encoding.

Although I have written ocaml-protoc as a personal project, it has been
used successfully in a professional context to interface with apache mesos.


On Sat, Feb 10, 2018 at 8:10 PM Kenneth Adam Miller <
kennethadammiller@gmail.com> wrote:

> The space complexity is ridiculous (at least X^2, possibly 2^n), it isn't
> as convenient as any of the others in allowing you to derive your own
> specs, it's horribly written code that uses ref and doesn't conform to
> OCaml conventions, it caused a lot of crashing on our end, only works for a
> particular compile target until I went to update it, the Makefile is an
> awful unmaintainable and unreadable mess, the language it defines is
> unnecessary and it's hard to get anything to change.
>
> We (me and some team mates) had this forced on us for the features we
> required, which was to be able to get data in and out of ocaml to other
> languages, and wanted to use it for a large project. It ended up causing a
> lot of unnecessary and unwanted slow down in development, both for our
> cases and for CMU's BAP. They had the same problems, and everyone that has
> touched it had to do unwanted work trying to get it to reliably do what it
> advertises.
>
> On Sat, Feb 10, 2018 at 7:43 PM, Louis Roché <mail@louisroche.net> wrote:
>
>> Can you give more details please ?
>
>
>>
>> > On 11 Feb 2018, at 04:56, Kenneth Adam Miller <
>> kennethadammiller@gmail.com> wrote:
>> >
>> > **Dont use piqi!** It's really terrible code.
>>
>

[-- Attachment #2: Type: text/html, Size: 2684 bytes --]

  reply	other threads:[~2018-02-11  2:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-10 18:05 picflo_2
2018-02-10 18:56 ` Kenneth Adam Miller
2018-02-11  0:43   ` Louis Roché
2018-02-11  1:09     ` Kenneth Adam Miller
2018-02-11  2:15       ` Maxime Ransan [this message]
2018-02-11 14:15         ` Aw: " picflo_2
2018-02-11 15:00           ` Daniil Baturin
2018-02-11 15:01           ` Maxime Ransan
2018-02-11 15:14             ` Aw: " picflo_2
2018-02-10 18:59 ` Daniil Baturin
2018-02-11 12:16 ` SP

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGOKm=S9Mb--zV0_qA9zKN1Oy=-eotGoQx6+Rd+n77yDM=Nv6A@mail.gmail.com' \
    --to=maxime.ransan@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=kennethadammiller@gmail.com \
    --cc=mail@louisroche.net \
    --cc=picflo_2@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).