From: bob zhang <bobzhang1988@gmail.com>
To: oliver <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Need help for a practical hacking book about ocaml
Date: Sat, 24 Dec 2011 22:56:35 -0500 [thread overview]
Message-ID: <CANcqPu7wnVKkHAqPa13r9zGTwehdOgi1t9O5eq+z_T3_eiC0RA@mail.gmail.com> (raw)
In-Reply-To: <20111225031134.GF1752@siouxsie>
[-- Attachment #1: Type: text/plain, Size: 1910 bytes --]
Thanks.
About why ocaml is more productive, probably my explanation will cause a
flaming war, so
correct me if I am wrong.
Of course, I understand monad, arrow, frp, TH, ST monad or other topics in
haskell, but that
does not really help solve the *real wolrd problems*. And laziness/purity
is really a big hurt.
I think what helps is we could share our tricks programming with ocaml,
some nice tricks or
techniques really help boost productivity. For example, I wrote a tiny
toplevel library (like hoogle
for haskell), I found it really helps.
My experience in ocaml limited, and the documentation of ocaml is really
lacking, so I think sharing
will help the small community.
I wrote the docs using latex, I digged muse tonight, I can htmlized it, if
that could help sharing.
I would publish it to github after Christmas.
Merry XMas :-)
On Sat, Dec 24, 2011 at 10:11 PM, oliver <oliver@first.in-berlin.de> wrote:
> Hello,
>
> On Sat, Dec 24, 2011 at 04:55:26PM -0500, bobzhang wrote:
> [...]
> > My book mainly focus on how to make ocaml programmers more productive,
> > quite different from other existing books.
> [...]
>
> A good idea.
>
> [...]
> > I have been digging haskell, ocaml, lisp for several years, honestly
> > speaking, I found ocaml is still the most productive language.
> [...]
>
> You could put the above paragraph into the preface.
> And mention, that even you found OCaml to be the most
> productive language, you even want to become more productive,
> and that was the reason for your book... (that's what I understood).
>
> Maybe you could elaborate a littlebid more about why you
> think that OCaml is most productive.
> It's of course also my conclusion from looking at a lot of languages.
> But you might be better in explaining it.
>
> You asked for help.
> Can you specify more detailed, which kind of help you are looking for?
>
> Ciao,
> Oliver
>
--
Best, bob
[-- Attachment #2: Type: text/html, Size: 2629 bytes --]
next prev parent reply other threads:[~2011-12-25 3:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-24 21:55 bobzhang
2011-12-25 1:25 ` Alex Rubinsteyn
2011-12-25 1:38 ` bob zhang
2011-12-25 3:11 ` oliver
2011-12-25 3:56 ` bob zhang [this message]
2011-12-25 12:15 ` rixed
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=CANcqPu7wnVKkHAqPa13r9zGTwehdOgi1t9O5eq+z_T3_eiC0RA@mail.gmail.com \
--to=bobzhang1988@gmail.com \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.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