From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] caml trading
Date: Mon, 16 Mar 2009 17:38:35 +0000 [thread overview]
Message-ID: <200903161738.35576.jon@ffconsultancy.com> (raw)
In-Reply-To: <594f78210903161001k685fc9ccnb4f566c342e2bfca@mail.gmail.com>
On Monday 16 March 2009 17:01:15 aditya siram wrote:
> Thanks for this awesome video! I was unaware that the Caml compiler did not
> optimize source code before generating native code. Now I am a little less
> afraid to study the actual compiler!
The OCaml compilers are remarkably comprehensible. I attribute that to the
OCaml developers at INRIA discarding implementations of ideas that turned out
to be rubbish rather than accumulating such cruft. So there is very little
irrelevant baggage in there compared to many other compilers.
> Your point about a lack of GUI libraries is great - however it seems as
> though they are not as important as they once were. The amazing javascript
> toolkits [1] that have sprung up over the last year (along with the Ocsigen
> and OBrower project [2]) have filled most of that vaccum.
>
> As long as there are libraries that provide an easy way to hook up with a
> web client is there still a compelling reason to develop native GUI
> toolkits?
Performance. If you want to do OpenGL-based visualization then you at least
need a fast route from the high-level data you are visualizing through to a
low-level representation (e.g. tesselations) down to the C FFI to the OGL
driver. Javascript is, of course, not up to the task. OCaml is much better
but there is still room for improvement.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2009-03-16 17:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 19:52 Yaron Minsky
2009-03-14 0:56 ` [Caml-list] " Yoann Padioleau
2009-03-14 17:25 ` Yaron Minsky
2009-03-16 14:24 ` Yoann Padioleau
2009-03-16 14:30 ` Jim Miller
2009-03-16 18:35 ` Yaron Minsky
2009-03-16 18:55 ` Andres Varon
2009-03-16 15:31 ` Markus Mottl
2009-03-17 2:37 ` David Baelde
2009-03-17 3:06 ` Alexy Khrabrov
2009-03-17 3:22 ` Yaron Minsky
2009-03-17 13:56 ` Markus Mottl
2009-03-17 15:26 ` Mike Lin
2009-03-17 17:14 ` Xavier Leroy
2009-03-17 17:05 ` Lawrence Austen
2009-03-17 22:35 ` xahlee
2009-03-18 10:38 ` Philippe Veber
2009-03-19 9:49 ` Loup Vaillant
2009-03-17 11:34 ` Kuba Ober
2009-03-16 23:23 ` Mike Lin
2009-03-14 7:25 ` Jon Harrop
2009-03-15 18:26 ` Yaron Minsky
2009-03-14 19:30 ` Jim Miller
2009-03-15 18:20 ` Yaron Minsky
2009-03-16 17:01 ` aditya siram
2009-03-16 17:38 ` Jon Harrop [this message]
2009-03-17 7:27 ` Philip
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=200903161738.35576.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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