From: "Jon Harrop" <jon@ffconsultancy.com>
To: "'Daniel Bünzli'" <daniel.buenzli@erratique.ch>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] Re: Haskell vs OCaml
Date: Sat, 23 Mar 2013 01:15:34 -0000 [thread overview]
Message-ID: <01fb01ce2763$ec22c3f0$c4684bd0$@ffconsultancy.com> (raw)
In-Reply-To: <29025F595E9343479E21A54CC92048AA@erratique.ch>
Daniel Bunzli wrote:
> Unless I'm mistaken, here around when we say 100% pure OCaml code,
> it means code that uses the standard library, 100% pure OCaml modules
> and no C bindings or unsafe features like Obj.
> AFAIK labgl is not part of the OCaml system. If that software layer was
> key to your product you should have ensured that you had some
> understanding/control of it -- even if that meant writing your own.
How do you reconcile having to reinvent the wheel by writing my own OpenGL bindings with Yaron's assertion that OCaml is "highly productive"?
> More than that you should have realized that while lablgl is fine for
> hobby opengl programming, it has obvious shortcomings that makes
> it ill suited to develop products on top of it.
What shortcomings?
> It seems you did something wrong in building your product...
Only when I was building my product using OCaml. When I was building my product using F# instead I apparently didn't do anything wrong.
Cheers,
Jon.
next prev parent reply other threads:[~2013-03-23 1:15 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
2013-03-23 1:41 ` oliver
2013-03-23 1:15 ` Jon Harrop [this message]
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='01fb01ce2763$ec22c3f0$c4684bd0$@ffconsultancy.com' \
--to=jon@ffconsultancy.com \
--cc=caml-list@inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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).