caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: [off-topic] was Re: [Caml-list] New Ocaml Plug-in for NetBeans
Date: Sat, 26 Jul 2008 13:17:55 +0100	[thread overview]
Message-ID: <20080726121755.GA30209@annexia.org> (raw)
In-Reply-To: <200807261240.10757.jon@ffconsultancy.com>

On Sat, Jul 26, 2008 at 12:40:10PM +0100, Jon Harrop wrote:
> Yet Make is not expressive enough so we have OMake, OCamlBuild...

Make is perfectly expressive enough.

When you start an OCaml project, you certainly need to know a bunch of
stuff to write the autoconf/make framework, and it's not very well
documented.  Almost everyone starts from an existing project -- I
suggest starting from here[1].  IDEs let you start a project much more
easily because they write the boilerplate.

Ah but here's the problem: the boilerplate is meaningful, and sooner
or later you'll need to change it (eg. your project has some complex
code generation or you want to script some automated tests).  Now your
IDE is getting in the way, your beginner has to face all that "stuff"
which was hidden behind the scenes, and (in one IDE I used) you
couldn't edit the boilerplate at all!

Not to mention serious real world problems like collaborating with
people who don't want to use the IDE, version control, cross-
compiling, applying patches, making tarballs & RPMs, uploading to your
website, feeding patches back upstream, integration with l10n tools,
etc.  Most of which are way beyond what IDEs offer.

If you think the good people who develop libvirt could do it using an
IDE, you really don't understand the scope of the problem:

http://git.et.redhat.com/?p=libvirt.git;a=tree
http://git.et.redhat.com/?p=libvirt.git;a=blob;f=configure.in;h=8e04f14131cf68de6eee6eadd05c5704ea8a5d41;hb=HEAD
http://git.et.redhat.com/?p=libvirt.git;a=blob;f=Makefile.am;h=b5082d6a7eaf7c746c3e52d61f6eb952df79db42;hb=HEAD

Rich.

[1] http://hg.et.redhat.com/virt/applications/virt-top--devel click 'manifest'

-- 
Richard Jones
Red Hat


  parent reply	other threads:[~2008-07-26 12:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26  9:02 hmf
2008-07-26  9:19 ` Richard Jones
2008-07-28  9:58   ` Florian Hars
2008-07-26 10:03 ` Erik de Castro Lopo
2008-07-26 11:40   ` Jon Harrop
2008-07-26 12:07     ` Erik de Castro Lopo
2008-07-26 15:22       ` Jon Harrop
2008-07-29 14:16         ` Damien Doligez
2008-07-29 14:30           ` Lukasz Stafiniak
2008-07-29 18:01             ` Jean-Christophe Filliâtre
2008-07-26 12:17     ` Richard Jones [this message]
2008-07-26 15:51       ` [off-topic] was " Jon Harrop
2008-09-07 21:39     ` Nathaniel Gray
2008-07-26 11:42 ` Jon Harrop

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=20080726121755.GA30209@annexia.org \
    --to=rich@annexia.org \
    --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).