Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Gour <gour@atmarama.net>
To: caml-list@inria.fr
Subject: [Caml-list] UFO (United Forces of OCaml)
Date: Fri, 27 Sep 2013 09:11:46 +0200	[thread overview]
Message-ID: <20130927091146.54ef8c42@atmarama.noip.me> (raw)

Hello,

I'm at the beginning of learning and using OCaml which is very fine
language and I've decided to use it over Ada.

Many new things are happening like development of OPAM (very nice
project), then moving some projects to ocaml.org subdomains, new design
of the site as well...

However, there are certain things which seems like wasting of resources,
so my humble proposal is whether it is possible to make UFO - United
Forces of OCaml in order not to have too many (similar) projects
tackling the same problems.

One area which quickly comes to my mind is standard library. Although
I'm not (yet) able to conclude how much is standard library incomplete,
I see there are two larger projects trying to fill the gap.

Jane Street is calling it "'Jane Street's alternative to the standard
library", while 'batteries' are labelled as: "community-driven effort to
standardize on an consistent, documented, and comprehensive development
platform for the OCaml programming language."

For the uninitiated it's seems as attempts to solve the same problem,
but, unfortunately, it looks they're tackling it in a non-compatible
way.

It's especially sensitive considering that the RWO book -  which might
be used for many noobs to learn the language - is promoting Core, while
'community-driven' project is working on something else.

Another thing which I can think of are build systems and although I'm
aware there is certain overlap in functionality and/or interdependances,
to me it seems that there are too many of them:

a) OASIS

b) ocamlbuild

c) omake

d) ocp-build

e) yenga

f) ...

The list can be, of course, annotated by the need to have actively
developed/maintained bindings for truly multio-platform GUI bindings
(e.g. wx/Qt).

So, my naive proposal is to try to combine forces together and produce
small(er) set of tools libraries and make it somewhat 'standard' within
community. It will attract new people to the language itself by making
it (more) clear what are the standard tools to be used.

The OCaml community is, imho, not big-enough to allow such luxury of
re-inventing the wheels...

Moreover, OCaml is advertised as "general purpose industrial-strength
programming language" and it behooves to have mature fully baked
ecosystem.


Sincerely,
Gour

-- 
The work of a man who is unattached to the modes of material 
nature and who is fully situated in transcendental knowledge 
merges entirely into transcendence.

http://www.atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810



             reply	other threads:[~2013-09-27  7:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27  7:11 Gour [this message]
2013-09-27 11:20 ` Török Edwin
2013-09-27 12:04   ` Yaron Minsky
2013-09-27 12:15     ` Paolo Donadeo
2013-09-27 15:55       ` David MENTRE
2013-09-27 16:25         ` Siraaj Khandkar
2013-09-27 16:45           ` Ashish Agarwal
2013-09-27 12:13   ` Gour
2013-09-27 11:25 ` Lukasz Stafiniak
2013-09-30  1:40 ` Francois Berenger
2013-09-30  6:01   ` Gour
2013-09-30  6:33     ` Francois Berenger
2013-09-30 14:14   ` Sylvain Le Gall
2013-09-27 17:08 Damien Guichard
2013-09-27 18:58 ` Gour

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=20130927091146.54ef8c42@atmarama.noip.me \
    --to=gour@atmarama.net \
    --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