From: Roberto Di Cosmo <roberto@dicosmo.org>
To: Thomas Braibant <thomas.braibant@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Distributed computing libraries
Date: Wed, 6 Jun 2012 22:24:02 +0200 [thread overview]
Message-ID: <20120606202402.GA19265@voyager> (raw)
In-Reply-To: <CAHR=VkxRi3G3mtgCmWqByGirJZNjM6vv6y26RKmUsj_wXmnJ_g@mail.gmail.com>
On Wed, Jun 06, 2012 at 12:53:07PM -0400, Thomas Braibant wrote:
<snip>
> Maybe it would be interesting for the community if someone could sum
> up the pros and cons of each of this "libraries", and maybe give some
> information about their status (still in development, mature, etc)?
>
> With best regards,
> Thomas Braibant
Quite a good point, and it really goes beyond just the bunch of
(very useful) libraries that try to speed-up computations by
leveraging multicore/multiprocessors/clusters etc.
I think OCaml is a wonderful language, and it has the potential
to attract much more users if we can make it easy to find, build,
install, compare and assess the various libraries, packages
and tools that are available.
If I can dream with my eyes open (which is a decent way of
spending time while waiting for a plane in the middle
of Nebraska, after all :-)), I could imagine:
(1) a central repository for OCaml projects where
packages are uploaded, with their different versions, tagged,
and classified, with pointers to the current, active development
platform (github, gitorious, sourceforge, whatever) (Oasis DB?)
(2) a continuous integration server testing buildability of the
different versions of the packages, with different versions
of the compiler, and on all available architectures, reporting
errors in a meaningful way to their authors, and providing
extremely valuable information to users that will know
beforehand what works and what does not work on which
configuration, instead of discovering this the hard way
(Debian OCamlers lurking here surely know what is the source
of inspiration of this part of my dream; and yes, Debian does
all this for the Debian OCaml packages, but we need to cater
to *all* users :-))
(3) an organised OCamlPedia site where, for each 'class' of
problem (parallelism, parsing, graph algorithms, numerical
computation, code transformation, you name it) developers and users
can contribute to maintain up-to-date summaries, comparisons,
test results, code snippets, pointers to scientific papers
and the like...
And for each "feature" of the language, I'd love to see tutorials,
code examples, pointers to the relevant literature, and to
packages showing them off.
To get there, we need to make our collaborative hidden side shine,
and complete the effort started by some of us to organise the community...
maybe this will happen during the coffee break at the next OCaml meeting.
Ok, time to stop dreaming, to go back to reality, and to catch that flight
--Roberto
P.S.: hey, I just checked, and ocamlpedia.* is available,
so I registered ocamlpedia.org, and I'll be more than happy
to offer it to whomever will run the site, if it happens :-)
next prev parent reply other threads:[~2012-06-06 20:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 16:53 Thomas Braibant
2012-06-06 17:31 ` oliver
2012-06-06 17:34 ` Vincent Aravantinos
2012-06-06 18:01 ` AW: " Gerd Stolpmann
2012-06-06 18:16 ` Edgar Friendly
2012-06-06 18:18 ` oliver
2012-06-06 18:35 ` AW: " Gerd Stolpmann
2012-06-06 18:44 ` Edgar Friendly
2012-06-06 20:52 ` Thomas Braibant
2012-06-07 1:34 ` Francois Berenger
2012-06-07 15:44 ` Thomas Braibant
2012-06-08 0:53 ` Francois Berenger
2012-06-08 6:36 ` Francois Berenger
2012-06-06 20:24 ` Roberto Di Cosmo [this message]
2012-06-06 20:43 ` Thomas Braibant
2012-06-07 1:48 ` [Caml-list] OCaml package managers Francois Berenger
2012-06-06 22:23 ` [Caml-list] Distributed computing libraries Ashish Agarwal
2012-06-08 6:55 ` Roberto Di Cosmo
2012-06-11 14:48 ` Ashish Agarwal
2012-06-08 8:58 ` jean-marc alliot
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=20120606202402.GA19265@voyager \
--to=roberto@dicosmo.org \
--cc=caml-list@inria.fr \
--cc=thomas.braibant@gmail.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