From: "Richard W.M. Jones" <rich@annexia.org>
To: achrist@easystreet.net
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Questions about OCaml and google native client
Date: Wed, 21 Dec 2011 23:54:55 +0000 [thread overview]
Message-ID: <20111221235455.GA21379@annexia.org> (raw)
In-Reply-To: <20111221232859.GA21209@annexia.org>
On Wed, Dec 21, 2011 at 11:28:59PM +0000, Richard W.M. Jones wrote:
> On Sat, Dec 17, 2011 at 07:45:21AM +0100, achrist@easystreet.net wrote:
> > I have just been reading about google native client, and it seems
> > like it may be a fun platform for which to write something. OCaml
> > looks like the best language on there so far. Questions about it:
I guess I'll answer the questions, by looking at the code itself ...
> > 1. How alive is the project of supporting OCaml on google NACL?
Not very alive, by the looks of it. However ...
> > The version of OCaml supported there is 3.11 from what I could
> > find, several months behind current release. Anyone know if and
> > when this will get brought up to date?
... the patch to ocamlopt is really small. Possibly even a candidate
for going upstream. So updating it to the latest OCaml 3.12 ought to
be very simple.
The current patch only implements the changes for i386. For OCaml in
particular since 64 bit is so useful, it'd be nice to have an
equivalent patch for the x86-64 backend. That's also probably not
hard, although the sandboxing techniques for i386 and x86-64 used by
NaCL are reportedly quite different.
> > 2. Are there any particularly good OCaml programs now available
> > that run in google NACL? Any nice ones available from the google
> > app store?
No idea ...
> > 3. Any other thoughts about the viability of this combination?
NaCL is a fantastic concept actually. It's a bit of a shame that
other browser vendors seem to be steering clear, although there does
seem to be a plugin.
So having an OCaml backend (and other functional languages) is a
thoroughly good thing IMHO. It could finally offer a clean break from
Javascript / targeting Javascript, while allowing web programs to run
at full speed and be written in reasonable languages.
A possible downside is current lack of portability to non-x86 &
non-ARM platforms. (NaCL supports i386, x86-64 and ARM only).
Here's an introduction to how NaCL works:
http://research.google.com/pubs/archive/34913.pdf
Rich.
--
Richard Jones
Red Hat
prev parent reply other threads:[~2011-12-21 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 6:45 achrist
2011-12-21 23:28 ` Richard W.M. Jones
2011-12-21 23:54 ` Richard W.M. Jones [this message]
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=20111221235455.GA21379@annexia.org \
--to=rich@annexia.org \
--cc=achrist@easystreet.net \
--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;
as well as URLs for NNTP newsgroup(s).