caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Alexy Khrabrov <deliverable@gmail.com>
Cc: txr@alumni.caltech.edu, caml-list@yquem.inria.fr,
	Jason Hickey <jyh@cs.caltech.edu>
Subject: Re: [Caml-list] The new OCaml book (Objective Caml Programming	Language by Tim Rentsch)
Date: Mon, 02 Mar 2009 19:37:41 +0100	[thread overview]
Message-ID: <49AC2775.1060005@inria.fr> (raw)
In-Reply-To: <A5E742AF-C71A-436C-BC5E-8BD64696A656@gmail.com>

> Overall, I can't help seeing that any author who isn't known on this
> list ends up with a questionable book -- first Smith and now Rentsch. 
> Perhaps the elders should form a book vetting committee?

Well, the power to decide is in the hands of publishers (initially)
and customers (later).  But I can assure you that reputable publishing
houses like Springer, Cambridge University Press or MIT Press do
sollicit opinions from academics like me and take them into account.
Their area editors attend major conferences like Principles of
Programming Languages and it's always a pleasure to chat with them.
But there isn't much that can be done with less reputable publishers
and self-publishing, as Alexy remarked.

Coming back to the Hickey/Rentsch book(s), I feel deeply sad about
the mess that is unfolding on this list.  I proofread a draft of Jason
Hickey's book, at his request, and found it very good and just what
the OCaml community is still missing: a well-written, English-language
book on Caml appropriate both as a reference and as teaching material.
(I'm not criticizing the other books in english on OCaml -- thanks God
they exist! -- just noting that they don't quite fit this exact purpose.)
What we now have is lawsuit material...  I sincerely hope some kind of
agreement can still be found at this point.

- Xavier Leroy


  reply	other threads:[~2009-03-02 18:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 16:21 Tim Rentsch
2009-03-02 18:06 ` Alexy Khrabrov
2009-03-02 18:37   ` Xavier Leroy [this message]
2009-03-03  1:29     ` Jon Harrop
2009-03-04  7:58     ` Tim Rentsch
2009-03-04  6:59   ` Tim Rentsch
2009-03-04  8:06     ` Stefano Zacchiroli
2009-03-05  2:57       ` Jason Hickey
2009-03-05  3:17         ` Jason Hickey
  -- strict thread matches above, loose matches on Subject: below --
2009-03-04 13:39 Ed Keith
2009-02-28 17:17 Tim Rentsch
2009-02-27 12:27 Richard Jones
2009-02-27 12:29 ` [Caml-list] " Richard Jones
2009-02-27 14:28 ` Tom Hutchinson
2009-02-27 19:40   ` Jon Harrop
2009-02-27 20:22     ` Jason Hickey
2009-02-27 21:34       ` Jon Harrop
2009-02-27 21:48         ` Dario Teixeira
2009-02-28 14:19         ` Jon Harrop
2009-02-27 23:34       ` Richard Jones
2009-02-28 17:52       ` Tim Rentsch
2009-02-27 17:37 ` Nathaniel Gray
2009-02-27 17:42   ` Richard Jones
     [not found]     ` <aee06c9e0902271043g419a0581mf17430b55a695f2b@mail.gmail.com>
2009-02-27 18:45       ` Nathaniel Gray
2009-02-27 18:52         ` William Neumann
2009-02-27 20:06           ` Jon Harrop
2009-02-27 23:29           ` Richard Jones
2009-02-27 17:46   ` Alexy Khrabrov

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=49AC2775.1060005@inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@yquem.inria.fr \
    --cc=deliverable@gmail.com \
    --cc=jyh@cs.caltech.edu \
    --cc=txr@alumni.caltech.edu \
    /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).