caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Gerd Stolpmann" <info@gerd-stolpmann.de>
To: "Alexandre Pilkiewicz" <alexandre.pilkiewicz@polytechnique.org>
Cc: "ivan chollet" <ivan.chollet@gmail.com>,
	"Benedikt Meurer" <benedikt.meurer@googlemail.com>,
	caml-list@inria.fr
Subject: Re: [Caml-list] OCaml maintenance status / community fork
Date: Tue, 6 Dec 2011 16:10:19 +0100	[thread overview]
Message-ID: <7b8a9e9bba71a1be49e46deb008bcb6e.squirrel@gps.dynxs.de> (raw)
In-Reply-To: <CAH2fdNbGjNUBGOWk=a8jd1JQ9WG1HN-bZtCknse6=Be=J12EVQ@mail.gmail.com>


> Hi all,
>
> I will not jump in the "how to save OCaml from dying because nothing
> moves" discussion. But just in the "nothing moves" discussion.
>
> On Tue, Dec 6, 2011 at 2:52 PM, ivan chollet <ivan.chollet@gmail.com>
> wrote:
>> The current status of OCaml is more than stable enough to serve its
>> goals,
>> which are to teach computer science to french undergrads and provide a
>> playground for computer languages researchers.
>
> First, french undergrads sadly often still use camllight... Which is
> not the case for example of Harvard undergrad
> (http://www.seas.harvard.edu/courses/cs51/lectures.html) and some
> UPenn one (http://www.seas.upenn.edu/~cis341/). But you are right that
> I can't find any well known university out of France using OCaml to
> teach computer science...

Well, if you ask whether _any_ FP language is taught, the results won't be
much better.

I'm currently doing consulting for a web company (in Germany) - around 60
developers, many fresh from the University. There are only three guys
knowing FP languages at all - one Scala, one Erlang, and one R. It's a
complete failure of the academic education.

IMHO it does not matter which FP language you are taught in. The point is
that the students understand the ideas, and that they recognize them as
relevant. These web developers here in the company have no clue that they
actually developing a big continuation-style FP program.

Gerd


>
> And for the "computer languages researchers" part, I'll refer you to
> http://caml.inria.fr/consortium/
>
>> A fork could possibly get traction from the community, but you would
>> have to
>> provide interesting features that the real OCaml does not provide. Bug
>> fixes
>> won't be enough.
>
> So now, here is my real problem. What are those famous so wanted
> feature that this fork will provide? And what makes you (a plural you)
> think that ocaml is such a slowly moving and evolving language?
> According to the caml web site, in the past two years, we've seen
> native dynlink, polymorphic recursion and first class module making
> there way into the language. According to what can be found on the
> trunk of the ocaml svn, the next release will have GADTs. And the
> compiler have also been modified to incorporate things like a nice
> multiprecision library (http://forge.ocamlcore.org/projects/zarith/)
> and some backends have been added.
>
> Except maybe haskell and Scala, can you really name me a programming
> language that in fact evolves that quickly, and basically without ever
> breaking backward compatibility? I really don't think that any of
> python, perl, java, C, C++ would really win. But I might be wrong.
>
> So before saying we need to fork the OCaml compiler to add "much
> needed patches", it would be nice to minimally agree on witch patches
> are so much needed. Because if "the community" can't agree on this, I
> doubt the future of this potential fork will be so bright.
>
> My 2c.
>
> --
> Caml-list mailing list.  Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
>


-- 
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
*** Searching for new projects! Need consulting for system
*** programming in Ocaml? Gerd Stolpmann can help you.



  reply	other threads:[~2011-12-06 15:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  8:25 Benedikt Meurer
2011-12-06  9:17 ` Goswin von Brederlow
2011-12-06 10:08   ` Gaius Hammond
2011-12-06  9:31 ` rixed
2011-12-06 12:10   ` Benedikt Meurer
2011-12-06  9:42 ` Kakadu
2011-12-06  9:48   ` Joel Reymont
2011-12-06 10:51   ` Fabrice Le Fessant
2011-12-06 10:58     ` Stefano Zacchiroli
2011-12-06 16:12       ` Fabrice Le Fessant
2011-12-06 19:24         ` Mehdi Dogguy
2011-12-06 10:00 ` Gerd Stolpmann
2011-12-06 12:20   ` Benedikt Meurer
2011-12-06 10:35 ` Gabriel Scherer
2011-12-06 11:31   ` Gerd Stolpmann
2011-12-06 12:34     ` Benedikt Meurer
2011-12-15 18:49     ` Jérôme Benoit
2011-12-06 13:09   ` Goswin von Brederlow
2011-12-06 22:48   ` oliver
2011-12-07  7:23     ` Adrien
2011-12-06 11:40 ` Gabriel Scherer
2011-12-06 12:02   ` Stefano Zacchiroli
2011-12-06 12:16     ` Joel Reymont
2011-12-06 12:43       ` Stefano Zacchiroli
2011-12-06 12:27   ` François Bobot
2011-12-06 13:01   ` Benedikt Meurer
2011-12-06 13:52 ` ivan chollet
2011-12-06 14:42   ` Alexandre Pilkiewicz
2011-12-06 15:10     ` Gerd Stolpmann [this message]
2011-12-06 15:14       ` Yitzhak Mandelbaum
2011-12-06 15:24         ` Pierre-Alexandre Voye
2011-12-07  9:36       ` Goswin von Brederlow
2011-12-06 22:07 ` oliver
2011-12-07  9:39   ` Goswin von Brederlow
2011-12-07 20:42     ` oliver
     [not found] <201112071100.pB7B0N8J020839@walapai.inria.fr>
2011-12-07 13:59 ` tools
2011-12-07 14:37   ` Jérémie Dimino

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=7b8a9e9bba71a1be49e46deb008bcb6e.squirrel@gps.dynxs.de \
    --to=info@gerd-stolpmann.de \
    --cc=alexandre.pilkiewicz@polytechnique.org \
    --cc=benedikt.meurer@googlemail.com \
    --cc=caml-list@inria.fr \
    --cc=ivan.chollet@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;
as well as URLs for NNTP newsgroup(s).