caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Yaron Minsky <yminsky@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] caml trading
Date: Sun, 15 Mar 2009 14:26:16 -0400	[thread overview]
Message-ID: <891bd3390903151126h31b951c6rbe85effaf0e5bcc2@mail.gmail.com> (raw)
In-Reply-To: <200903140725.32884.jon@ffconsultancy.com>

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

On Sat, Mar 14, 2009 at 3:25 AM, Jon Harrop <jon@ffconsultancy.com> wrote:

> On Friday 13 March 2009 19:52:14 Yaron Minsky wrote:
> > For those who are interested, I just posted a video of a talk I gave at
> CMU
> > several weeks ago about Jane Street's use of OCaml.  This is an updated
> > version of the talk I gave at POPL last year.  Various people have
> > expressed an interest in showing the talk to their undergraduate classes,
> > so I thought it worth mentioning on the list.
>
> Very interesting. I do have a couple of points:
>
> . If you want to see shared-memory parallelism done right look at Cilk. It
> is
> both painless and incredibly efficient.


I know about Cilk, but I'll go back and look at it again.  Thanks for the
suggestion.


> . I don't know how F# handles nulls but it has never caused me a problem
> and
> I've used many .NET libraries from F# including MDX, WPF, XNA and, of
> course,
> the framework itself.


Interesting.  I haven't done a ton of F# hacking, so I don't know the
details, but several people who work at Jane Street have stubbed their toe
on this.  It's quite possible that it mostly just doesn't come up, if you
code in the appropriate style.

And as I tried to say in the talk, F# definitely has a lot to recommend it.
It's just not a good match for us.

y

[-- Attachment #2: Type: text/html, Size: 1886 bytes --]

  reply	other threads:[~2009-03-15 18:26 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 [this message]
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
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=891bd3390903151126h31b951c6rbe85effaf0e5bcc2@mail.gmail.com \
    --to=yminsky@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=jon@ffconsultancy.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).