From: Jeremy Bem <jeremy1@gmail.com>
To: caml-list@yquem.inria.fr, caml-news-weekly@lists.idyll.org
Subject: NaCl/OCaml (OCaml as a client-side web programming language)
Date: Thu, 4 Mar 2010 18:22:27 -0500 [thread overview]
Message-ID: <eed625c81003041522yb8415efg475b7ea5eda60fe2@mail.gmail.com> (raw)
Hello,
I'm pleased to announce the initial release of NaCl/OCaml, a version
of the native-code OCaml compiler whose output can be validated as
safe to run over the web. Together with the "Native Client" plug-in
under development at Google, this means that OCaml can now be used for
client-side web programming!
For more about Native Client, see http://code.google.com/p/nativeclient/.
For NaCl/OCaml, including a ray tracer demo, see
http://code.google.com/p/nacl-ocaml/.
Feedback is welcome and appreciated. Please feel free to email me,
report bugs at the project website, or email
nacl-ocaml-discuss@googlegroups.com.
Thanks,
Jeremy
next reply other threads:[~2010-03-04 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 23:22 Jeremy Bem [this message]
2010-03-05 1:28 ` [Caml-list] " Daniel Bünzli
2010-03-05 1:37 ` Jeremy Bem
2010-03-05 9:36 ` David Rajchenbach-Teller
2010-03-05 11:47 ` Vincent Balat
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=eed625c81003041522yb8415efg475b7ea5eda60fe2@mail.gmail.com \
--to=jeremy1@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=caml-news-weekly@lists.idyll.org \
/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