Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Benedikt Meurer <benedikt.meurer@googlemail.com>
To: Gerd Stolpmann <info@gerd-stolpmann.de>
Cc: "Gabriel Scherer" <gabriel.scherer@gmail.com>,
	"caml users" <caml-list@inria.fr>
Subject: Re: [Caml-list] OCaml maintenance status / community fork
Date: Tue, 6 Dec 2011 13:34:10 +0100	[thread overview]
Message-ID: <D5D083F8-1776-4D92-831A-65675BF8D3E7@googlemail.com> (raw)
In-Reply-To: <4adc9f6482cdbe0208c0baf4992392de.squirrel@gps.dynxs.de>


On Dec 6, 2011, at 12:31 , Gerd Stolpmann wrote:

>> I would like to comment on a tangential aspect of the rationale you gave:
>> 
>>> Given that OCaml is such a nice language with a lot of useful frameworks
>>> available,
>>> it is too sad to see it loosing ground just because of it's closed
>>> development process
>>> and lack of time of the official team.
> 
> I'm quite reluctant to discuss topics about the said decline of something.
> However, there is certainly a point here. I have my own theory - basically
> the users with FP knowledge have now more options (e.g. F# or the
> JVM-based FP languages like Scala), and so the "share" for Ocaml is
> decreasing. This has nothing to do with the language.
> 
> However, the question is whether we can do more to attract programmers
> with FP knowledge (or even better educate programmers without). Ocaml is
> not doing enough here - there is no (really good) beginner's site, and
> there are not enough "success stories", i.e. users reporting that they
> solved something with Ocaml, and why it was a good choice.

Let me clarify what I mean: I think that both Gabriel and Gerd and right, and the success of OCaml does not solely depend on the openness of the compiler toolchain. Of course there's a lot more people can do to help with OCaml.

Now, I'm not particularly good at writing documentation or blogging about OCaml, but I can provide code and knowledge for the language implementation and in particular the compiler. And looking through Mantis there are others who are also willing to help with core stuff by sending patches, reporting bugs, etc. Unfortunately this is highly frustrating, as mentioned, because the OCaml core does not get a lot of love from the OCaml core team (for whatever reasons). Now you can move on and fork OCaml (Git makes that amazingly easy today) and add your patches, etc. We did this several times, and others also did. And the end you have the situation as we see it today: several forks with different goals / quality, various long standing bug reports with / without patches that don't get attention, almost no activity in the OCaml Subversion repository (as a result) compared to other active programming languages, and many frustrated contributors with time, interest and knowledge that would be really beneficial to OCaml otherwise.

> Gerd

Benedikt

  reply	other threads:[~2011-12-06 12:34 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 [this message]
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
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=D5D083F8-1776-4D92-831A-65675BF8D3E7@googlemail.com \
    --to=benedikt.meurer@googlemail.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@gmail.com \
    --cc=info@gerd-stolpmann.de \
    /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