From: Francois Berenger <berenger@riken.jp>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Haskell vs OCaml
Date: Tue, 19 Mar 2013 10:23:05 +0900 [thread overview]
Message-ID: <5147BDF9.8050003@riken.jp> (raw)
In-Reply-To: <CAGmVoG15XvxWb9SEkV_uj3v7SwB4r9W0K9=8UDPVEEGghkDBoQ@mail.gmail.com>
On 03/18/2013 08:26 PM, Kakadu wrote:
> Please, don't feed the troll
>
> On Mon, Mar 18, 2013 at 1:48 PM, Malcolm Matalka <mmatalka@gmail.com> wrote:
>> The biggest advantage for me is Ocaml is simpler than Haskell IMO.
>>
>> adrian.alexander.may@gmail.com writes:
>>
>>> On Wednesday, 13 August 2008 20:49:17 UTC+8, circ ular wrote:
>>>> What are the advantages/disadvantages when comparing OCaml to Haskell?
>>>
>>> case you of
>>> man -> haskell
>>> mouse -> ocaml
Last time I used it, the Haskell "ecosystem" around the language
(tools and libraries) was quite advanced (they had an OPAM-like
long time ago for example).
Also, the population of Haskell programmers might be bigger
(bigger open-source community, easier to find programmers to hire).
F.
next prev parent reply other threads:[~2013-03-19 1:23 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.e3jKyg6bl9+vTkPgypQ4ZRzEoos@ifi.uio.no>
2013-03-18 9:08 ` adrian.alexander.may
2013-03-18 9:48 ` Malcolm Matalka
2013-03-18 9:59 ` Gabriel Scherer
2013-03-18 11:05 ` Adrian May
2013-03-18 11:26 ` Kakadu
2013-03-18 18:05 ` [Caml-list] " Chet Murthy
2013-03-20 20:44 ` Jon Harrop
2013-03-20 21:10 ` Yaron Minsky
2013-03-21 0:26 ` Jon Harrop
2013-03-21 20:58 ` Yaron Minsky
2013-03-23 23:33 ` Richard W.M. Jones
2013-03-21 21:55 ` Török Edwin
2013-03-22 17:51 ` Jon Harrop
2013-03-22 18:46 ` Daniel Bünzli
2013-03-22 19:53 ` Jon Harrop
2013-03-22 20:23 ` Daniel Bünzli
2013-03-22 22:13 ` Jon Harrop
2013-03-22 23:35 ` Daniel Bünzli
2013-03-22 23:47 ` Chet Murthy
2013-03-23 0:02 ` Daniel Bünzli
2013-03-23 0:09 ` Chet Murthy
2013-03-23 1:17 ` Jon Harrop
2013-03-23 1:41 ` oliver
2013-03-23 1:15 ` Jon Harrop
2013-03-23 1:50 ` Daniel Bünzli
2013-03-25 1:22 ` Francois Berenger
2013-03-23 1:25 ` oliver
2013-03-19 1:23 ` Francois Berenger [this message]
2013-03-26 10:36 ` [Caml-list] " Nicolas Braud-Santoni
2013-03-26 0:49 ` Kristopher Micinski
2013-03-26 2:37 ` Erik de Castro Lopo
2013-03-26 2:57 ` Kristopher Micinski
2008-08-14 13:26 Damien Guichard
-- strict thread matches above, loose matches on Subject: below --
2008-08-13 12:48 circ ular
2008-08-13 13:27 ` [Caml-list] " Brian Hurt
2008-08-14 0:09 ` Jon Harrop
2008-08-14 2:46 ` David Thomas
2008-08-14 2:52 ` Erik de Castro Lopo
2008-08-14 10:37 ` Paolo Donadeo
2008-08-14 12:17 ` Jon Harrop
2008-08-14 16:44 ` Erik de Castro Lopo
2008-08-14 11:50 ` blue storm
2008-08-14 12:47 ` David Mitchell
2008-08-14 13:28 ` Peng Zang
2008-08-14 14:01 ` Peng Zang
2008-08-15 2:09 ` blue storm
2008-08-14 13:57 ` Jon Harrop
2008-08-14 14:06 ` Peng Zang
2008-08-14 14:21 ` Vincent Hanquez
2008-08-14 14:44 ` Jon Harrop
2008-08-14 20:57 ` Nicolas Pouillard
2008-08-14 21:16 ` Jon Harrop
2008-08-14 21:50 ` Nicolas Pouillard
2008-08-15 0:15 ` Jon Harrop
2008-08-15 1:14 ` Stéphane Glondu
2008-08-17 1:00 ` Luca Saiu
2008-08-19 2:40 ` Paul Snively
2008-08-20 11:33 ` Dr. Thomas Fischbacher
2008-08-21 8:47 ` DooMeeR
2008-08-21 10:59 ` David Teller
2008-08-21 13:52 ` Dr. Thomas Fischbacher
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=5147BDF9.8050003@riken.jp \
--to=berenger@riken.jp \
--cc=caml-list@inria.fr \
/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