caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Paolo Donadeo <p.donadeo@gmail.com>
To: OCaml mailing list <caml-list@inria.fr>
Subject: Re: [Caml-list] Some comments on recent discussions
Date: Wed, 7 Dec 2011 01:18:35 +0100	[thread overview]
Message-ID: <CAPzAKVCshB8mfN4t7i_LRiSMwHJk1vWoioHPz5u_2AWOTtwr9w@mail.gmail.com> (raw)
In-Reply-To: <4EDE568C.9040803@lexifi.com>

I just want to add some erratic thoughts summoned by the recent
<strike>flame</strike>... discussion about "the state of the OCaml
union". For this reason I'm not pretending to be coherent or to have
an answer to each and every problem, I'm not John Wayne and I'll never
be.

OCaml community is basically composed by computer professionals that
have very few time to spend on the geek social networks (reddit,
stackoverflow, ...) to write how this language is beautiful, how it is
so "pure" (or "impure"), and so on. I write software in OCaml, and
this software is working right now in a production environment.
Nothing even comparable with Jane St. or LexiFy or Mylife, but I have
my customers and if something stops working, they complain A LOT ;-)

This pragmatical attitude of the OCaml community is not accidental and
is the clear expression of a language that *is* pragmatical.

And this attitude is the main reason why, in my very honest opinion,
the OCaml language haven't a hype comparable to, say, Haskell. Is this
bad? Are we frustrated because nobody writes on "Wired" about OCaml?
I'm not.

What I like in OCaml is that it's really stable, fast and in the last
years many key tools have been added to the tool chain. As an
engineer, I think that ocamlbuild + oasis (only an example) are MORE
valuable than first class modules and GADTs. Which, in turn, are not
"minor improvements" at all, and I don't see this supposed immobility
of the language.

The standard library problem: the core library is small, ugly, useless
and more. The standard library provided by INRIA can't even send
email, make a POST, or talk with a web service. Ok, but what exactly
can you do with the C, or C++ standard library? I *like* the elegant
simplicity of the standard library and, when something is missing I
can: 1) write my own solution or 2) search for library by other OCaml
developers. What's wrong with Google searching for a good library? Why
many people seems to advocate a unique library "to rule them all"? And
why this huge library should enter in the standard distribution? Why
many people complain about the poor visibility of the community, but
refuses to use ocamlcore.org (thanks Sylvain forever!) only because
GitHub has a nicer web2.0 interface? Yes, I like GitHub, but I think
we *ALL* should host our projects, at least the main web pages on
OCamlCore, to minimize the scatter.

There are many specialized library for almost everything in OCaml, and
2/3 big "standard libraries" (Batteries, Core, ExtLib?). Why can't we
simply choose one of these excellent libraries? I like
<ads>Batteries</ads> but there is NOTHING wrong with Core, and I hope
both of them will remain OUT of the standard distribution forever.
Why? Because the standard library is small and virtually bug-free or,
better said, it tends to be so, because it's *rare* that a new feature
is added, and this is *good*. It's like the basic building blocks of
Lego: if you want gears or you need a pulley, buy Lego Technic ;-)

Another example: reactive programming. Not using Google (I swear!) I
can remember LWT, react, Ocamlnet (in part...) and froc. Is this
situation to be considered harmful? I appreciate this wide range of
approaches to the same problem, it's the sign of a vital community.

I'm too seasoned as a programmer and I already experienced the
<irony>huge benefits</irony> of big standard libraries: the
Magnificent Java Standard Library, BOOST, the ACE framework, and many
others, all excellent examples of what a serial killer can design with
a cohort of programmers and a beautiful programming language ;-)

I don't say there are no problems, and everything is fine. But if I
have do point at a problem, especially for newcomers, I would say that
we need a book, an up to date book, written in good English and
published by O'Relly.

But this is a very hard issue to be solved, no GitHub (R) (TM) in help here ;-)


-- 
Paolo

  reply	other threads:[~2011-12-07  0:19 UTC|newest]

Thread overview: 80+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06 15:24 Jonathan Protzenko
2011-12-06 15:31 ` Joel Reymont
2011-12-06 23:03   ` Martin Jambon
2011-12-06 16:01 ` Mihamina Rakotomandimby
2011-12-06 16:03 ` Benedikt Meurer
2011-12-06 16:56   ` Ashish Agarwal
2011-12-06 17:12 ` Gerd Stolpmann
2011-12-06 17:33 ` Alex Rubinsteyn
2011-12-06 17:53 ` Alain Frisch
2011-12-07  0:18   ` Paolo Donadeo [this message]
2011-12-07  1:00     ` oliver
2011-12-07  6:33       ` Mihamina Rakotomandimby
2011-12-07  1:48     ` Ashish Agarwal
2011-12-07  9:53       ` Goswin von Brederlow
2011-12-07 10:33     ` Pierre-Alexandre Voye
2011-12-07 11:18       ` Gabriel Scherer
2011-12-07 13:15         ` David MENTRE
2011-12-07 13:48           ` Alan Schmitt
2011-12-07 14:56           ` Ashish Agarwal
2011-12-07 15:52         ` oliver
2011-12-10 14:58         ` Xavier Leroy
2011-12-08  7:59       ` rixed
2011-12-08 10:37         ` oliver
2011-12-08 13:15         ` [Caml-list] Wanted book (Re: Some comments on recent discussions) Mihamina Rakotomandimby
2011-12-09 21:22           ` oliver
2011-12-09  7:13   ` [Caml-list] Some comments on recent discussions Martin Jambon
2011-12-10 20:32 ` Andrei Formiga
2011-12-10 21:01   ` Edgar Friendly
2011-12-10 21:12     ` rixed
2011-12-10 21:24       ` Edgar Friendly
2011-12-10 21:49         ` rixed
2011-12-10 22:45           ` Edgar Friendly
2011-12-10 23:58       ` Hans Ole Rafaelsen
2011-12-11 10:25       ` Gerd Stolpmann
2011-12-11 10:06   ` Gerd Stolpmann
2011-12-13 17:41   ` oliver
2011-12-13  5:54 ` Martin DeMello
2011-12-13  7:15   ` Gerd Stolpmann
2011-12-13  8:21     ` Martin DeMello
2011-12-13  8:51       ` Alain Frisch
2011-12-13  9:15         ` Gaius Hammond
2011-12-13 14:08           ` Gerd Stolpmann
2011-12-14  5:28           ` Alain Frisch
2011-12-13  9:51         ` Martin DeMello
2011-12-13  9:53         ` Adrien
2011-12-13 20:52           ` Jon Harrop
2011-12-14  6:03           ` Alain Frisch
2011-12-14  9:34             ` Jonathan Protzenko
2011-12-14 10:24               ` Alain Frisch
2011-12-14 13:37                 ` Adrien
2011-12-14 14:24                   ` Gabriel Scherer
2011-12-14 15:27                   ` Gerd Stolpmann
2011-12-14 15:46                     ` Gaius Hammond
2011-12-14 15:49                     ` Adrien
2011-12-14 16:42                       ` Fabrice Le Fessant
2011-12-14 17:04                       ` Alain Frisch
2011-12-15 21:38                         ` Adrien
2011-12-14 16:55                   ` Alain Frisch
2011-12-14 21:35                     ` Benedikt Meurer
2011-12-15 11:14                     ` Adrien
2011-12-14 12:52             ` Gerd Stolpmann
2011-12-14 13:25               ` Jonathan Protzenko
2011-12-14 17:27               ` Aleksey Nogin
2011-12-14 17:36                 ` Gerd Stolpmann
2011-12-14 19:41                   ` David Allsopp
2011-12-15 10:29                     ` Adrien
2011-12-15 17:41                       ` Martin DeMello
2011-12-15 20:47                         ` Adrien
2011-12-15 21:20                           ` Martin DeMello
2011-12-15 11:25                     ` Gerd Stolpmann
2011-12-16 12:39                   ` Alain Frisch
2011-12-16 12:44                     ` Jonathan Protzenko
2011-12-16 13:14                     ` Gerd Stolpmann
2011-12-16 14:11                       ` Alain Frisch
2011-12-16 14:50                         ` Gerd Stolpmann
2011-12-16 13:58                     ` Stéphane Glondu
2011-12-16 17:29                     ` Edgar Friendly
2011-12-14 18:41                 ` Dmitry Grebeniuk
2011-12-14 23:54               ` Martin DeMello
2011-12-15 10:03                 ` Adrien

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=CAPzAKVCshB8mfN4t7i_LRiSMwHJk1vWoioHPz5u_2AWOTtwr9w@mail.gmail.com \
    --to=p.donadeo@gmail.com \
    --cc=caml-list@inria.fr \
    /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).