From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pB6EgnDJ004661 for ; Tue, 6 Dec 2011 15:42:51 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AskAAGEp3k7RVdQ2kGdsb2JhbABEFqo+CCIBAQEBCQkNBxQEIYFyAQEBAQIBEgIsATgBAwELAQUFCw0uIQESAQUBHAYTFAoEh2UIl3wKjk+FK4kuAgUKiygElGaKZgKDBD2BS4It X-IronPort-AV: E=Sophos;i="4.71,306,1320620400"; d="scan'208";a="134178129" Received: from mail-vw0-f54.google.com ([209.85.212.54]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 06 Dec 2011 15:42:49 +0100 Received: by vbbfr13 with SMTP id fr13so8207462vbb.27 for ; Tue, 06 Dec 2011 06:42:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=FJf3E/ib/rOgEXURFhJi2e8GGnxKOki6Aq8wGWq/97I=; b=qmvqlYIrstReMkxATvvhe+PMAQwdeY2USZ+/JOjorqufCMMe89w3KPElsDK4hs+hQS 4zk5AIyEdwnnFPnnWvdW34ltn5WPQdD0jeIIMff30z0qX3QywckePMmf8sktAQ/r4V57 yFbVh//cM4f6XxbsXP88+jm1fVM59rPVmrrDM= Received: by 10.182.48.98 with SMTP id k2mr2094684obn.34.1323182569022; Tue, 06 Dec 2011 06:42:49 -0800 (PST) MIME-Version: 1.0 Sender: dapilki@gmail.com Received: by 10.182.112.66 with HTTP; Tue, 6 Dec 2011 06:42:25 -0800 (PST) In-Reply-To: References: <1B0D83BD-1902-4F7C-B3FB-B759122D6AB9@googlemail.com> From: Alexandre Pilkiewicz Date: Tue, 6 Dec 2011 15:42:25 +0100 X-Google-Sender-Auth: ZLjyEV989mW2B-K9y3jaCP52rHo Message-ID: To: ivan chollet Cc: Benedikt Meurer , caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Caml-list] OCaml maintenance status / community fork 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 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... 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.