From: Robert C Fischer <robert@fischerventure.com>
To: Richard Jones <rich@annexia.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Teaching bottomline, part 3: what should improve.
Date: Wed, 23 May 2007 14:27:24 -0500 [thread overview]
Message-ID: <4654959C.7040701@fischerventure.com> (raw)
In-Reply-To: <20070523185428.GA32681@furbychan.cocan.org>
...and locks and threads are not a viable long-term solution to the
problem of concurrency in general. You're future-proofing enough by
teaching them functional languages: Erlang and Cilk are closer to the
needed future.
~~ Robert.
Richard Jones wrote:
> On Wed, May 23, 2007 at 12:39:29AM +0100, Jon Harrop wrote:
>
>> If you want your students to be future proof then you would do well
>> to prepare them for massively parallel computing on CPUs with
>> hundreds or even thousands of cores. OCaml it completely
>> ill-equipped for this. In contrast, F# provides native
>> threads/locks/semaphores/threads/threadpools inherited from .NET as
>> well as async programming via extra syntax. Concurrency is beautiful
>> in F# and it works today.
>>
>
> F# scales to hundreds or thousands of cores?
>
> If the OP wants to teach his students about massively parallel
> computing, he should avoid the Microsoft lock-in and teach them about
> it on Linux clusters.
>
> Rich.
>
>
next prev parent reply other threads:[~2007-05-23 19:27 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 22:10 David Teller
2007-05-22 22:22 ` [Caml-list] " William D. Neumann
2007-05-23 13:07 ` David Teller
2007-05-22 22:26 ` Erik de Castro Lopo
2007-05-22 23:16 ` skaller
2007-05-23 2:46 ` David Thomas
2007-05-23 9:19 ` Vincent Hanquez
2007-05-23 12:49 ` Brian Hurt
2007-05-23 13:36 ` Gerd Stolpmann
2007-05-23 14:06 ` skaller
2007-05-23 14:54 ` Florian Hars
2007-05-23 15:11 ` Brian Hurt
2007-05-23 21:48 ` Vincent Hanquez
2007-05-24 8:04 ` Markus E.L.
2007-05-24 8:32 ` Vincent Hanquez
2007-05-24 9:51 ` skaller
2007-05-24 11:22 ` Vincent Hanquez
2007-05-23 13:55 ` David Teller
2007-05-22 23:19 ` skaller
2007-05-23 10:41 ` Richard Jones
2007-05-23 13:04 ` David Teller
2007-05-24 13:51 ` Richard Jones
2007-05-24 14:00 ` Robert Fischer
2007-05-24 14:00 ` Jon Harrop
2007-05-24 14:20 ` Robert Fischer
2007-05-24 14:34 ` David Teller
2007-05-24 14:21 ` skaller
2007-05-22 23:39 ` Jon Harrop
2007-05-23 18:54 ` Richard Jones
2007-05-23 19:27 ` Robert C Fischer [this message]
2007-05-23 19:34 ` Brian Hurt
2007-05-23 19:54 ` Robert Fischer
2007-05-23 21:46 ` Jon Harrop
2007-05-23 22:14 ` Jacques Garrigue
2007-05-24 1:38 ` Revolution Jon Harrop
2007-05-24 2:40 ` [Caml-list] Revolution skaller
2007-05-24 3:21 ` Chris King
2007-05-24 14:24 ` David Teller
2007-05-24 13:40 ` [Caml-list] Teaching bottomline, part 3: what should improve Brian Hurt
2007-05-23 19:29 ` Jon Harrop
2007-05-23 20:20 ` David Teller
2007-05-24 14:18 ` Jon Harrop
2007-05-24 14:23 ` skaller
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=4654959C.7040701@fischerventure.com \
--to=robert@fischerventure.com \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
--cc=robert.fischer@SmokejumperIT.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