caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jon Harrop" <jon@ffconsultancy.com>
To: "'Chet Murthy'" <murthy.chet@gmail.com>, <caml-list@inria.fr>
Subject: RE: [Caml-list] Re: Haskell vs OCaml
Date: Sat, 23 Mar 2013 01:17:33 -0000	[thread overview]
Message-ID: <01fc01ce2764$32e64e10$98b2ea30$@ffconsultancy.com> (raw)
In-Reply-To: <54562612.dHlMTtysyv@groupon>

Chet Murthy wrote:
> No OSS language runtime can afford that.
> ...
> This is hard, expensive, and will never happen for a language runtime
maintained by an open-source community.

That amount of effort might not be expected for such a language but I would
not neglect some opportunities that OCaml does have to improve this. For
example, LLVM and Clang could be used to help autogenerate bindings to C
libraries. That would be a big step up from where OCaml is today and would
yield dividends across the board.

> So .... why should you use ocaml instead of a CLR-based language (like
F#)?
> Well, as Daniel Bunzli said, maybe you shouldn't.

Exactly. Yaron's assertions that OCaml is highly productive, efficient and
reliably are not universally applicable. Which raises the question of when
they are applicable?

The OCaml distribution itself is certainly very reliable but is also very
limited in capability so I see no merit in restricting consideration to just
that. Indeed, LablGL was always reliable provided the code was compiled on
the machine it was run on and not distributed as a binary.

> But I would note that your experience would be no different if you were
> using Python, Perl, Ruby, or PHP.

I'm not convinced. I think part of the problem may have been linking between
statically-compiled OCaml code and libraries like OpenGL. With Python, the
OpenGL bindings would have been compiled for a specific binary distro which
might affect reliability.

Cheers,
Jon.



  parent reply	other threads:[~2013-03-23  1:17 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.e3jKyg6bl9+vTkPgypQ4ZRzEoos@ifi.uio.no>
2013-03-18  9:08 ` [Caml-list] " 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 [this message]
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       ` [Caml-list] " Francois Berenger
2013-03-26 10:36         ` 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

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='01fc01ce2764$32e64e10$98b2ea30$@ffconsultancy.com' \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@inria.fr \
    --cc=murthy.chet@gmail.com \
    /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).