caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jonathan Coupe" <jonathan@meanwhile.freeserve.co.uk>
To: <leary@nwlink.com>, <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml complexity
Date: Thu, 7 Jun 2001 19:29:27 +0100	[thread overview]
Message-ID: <002c01c0ef7f$e154f3e0$5d26883e@baby> (raw)
In-Reply-To: <20010607015821.B11344@jean>

> I'd wager that 90% of the reason Perl is so huge is due to _Learning
Perl_.
> Neophytes can start writing interactive programs on page 7.  I went from
> near zero programming ability to writing an IDL parser/EDI data tranlator
> in about a month or so using that and Programming Perl -- for which the
OCaml
> manual is a semi-reasonable, if terse and dry, match.  Is there hope for
> the coming O'Reilly translation, or does it too think that I/O (i.e. doing
> something useful and interesting) is something best left for the later
> chapters (or the reference section)?  It's hard for me to believe that
> OCaml can be both so good, and so unpopular (read: badly documented (read:
> no friendly tutorials)).  From whence _Learning OCaml_?

Books are important. Perl's are superb at getting a new user started. A
Learning OCaml would be a good thing. But Perl's spread is also dues to at
least four other factors:

1. Perl was perceived by the adopters who gave it critical mass as being
fundamentally like the languages they already knew (bash, C, Awk) It was a
low risk, low effort, low fear choice.

2. Perl is aimed most of all at small projects. The risk of trying new tools
in this space is low - throwing away a 200 lines of code is annoying, but
not job threatening. And benefits are quickly perceiveable. Ocaml's best use
is probably larger projects beyond the scope of scripting languages.
Throwing a way an even quarter completed project is likely to mean the loss
of several thousand lines of coding effort, and you're unlikely to have
proveable benefits until the end of the first project, which is more likely
to be months, not days or hours, after starting work.

3. Perl's regexp gave it a decisive edge in several rapidly expanding
niches.

4. Its easy to perceive Perl's strengths from an initial examination, and
perhaps harder to pick up on its weaknesses.


Jonathan Coupe

-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-06-07 18:24 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07  8:58 leary
2001-06-07 18:29 ` Jonathan Coupe [this message]
2001-06-08  9:41   ` leary
2001-06-08 10:05     ` Why is Ocaml better than Java (WAS: [Caml-list] ocaml complexity) Mattias Waldau
2001-06-08 13:31       ` Pierre Weis
2001-06-08 16:37         ` William Chesters
2001-06-08 21:39       ` Brian Rogoff
     [not found]       ` <Pine.BSF.4.21.0106081430070.27414-100000@shell5.ba.best.co m>
2001-06-08 22:16         ` Chris Hecker
2001-06-08 12:27     ` [Caml-list] ocaml complexity Jonathan Coupe
2001-06-08 20:22       ` Chris Hecker
2001-06-08 20:31         ` Miles Egan
2001-06-08 22:17           ` Jonathan Coupe
2001-06-08 22:18             ` Miles Egan
2001-06-11 14:05             ` Pierre Weis
2001-06-09 19:41           ` John Max Skaller
2001-06-08 22:59         ` David Fox
2001-06-09  0:43         ` leary
2001-06-09  1:09           ` Mark Wotton
2001-06-09  8:36           ` Markus Mottl
2001-06-09 20:58           ` John Max Skaller
2001-06-08 22:46       ` leary
2001-06-09  1:18         ` David Fox
2001-06-12 14:17           ` John Max Skaller
2001-06-13 15:21             ` Brian Rogoff
2001-06-13 20:32               ` leary
2001-06-13 22:58                 ` Johann Höchtl
2001-06-13 21:18               ` John Max Skaller
2001-06-09 22:32         ` Jonathan Coupe
2001-06-11  0:20           ` leary
  -- strict thread matches above, loose matches on Subject: below --
2001-06-14 16:04 John R Harrison
2001-06-13 21:04 David Gurr
2001-06-13 23:13 ` leary
2001-06-13 23:19 ` Brian Rogoff
2001-06-15 13:28   ` Tore Lund
2001-06-15 14:03     ` Nils Goesche
2001-06-15 14:54       ` Xavier Leroy
2001-06-15 15:14         ` Jonathan Coupe
2001-06-15 15:23         ` Nils Goesche
2001-06-15 17:38         ` Sven LUTHER
2001-06-15 20:36           ` Remi VANICAT
2001-06-15 14:16     ` Doug Bagley
2001-06-28 12:54   ` Didier Remy
2001-06-28 18:31     ` Brian Rogoff
2001-06-11 20:33 Arturo Borquez
2001-06-11 21:17 ` Miles Egan
2001-06-12  7:19   ` wester
2001-06-06 16:50 Miles Egan
2001-06-06 17:30 ` Chris Hecker
2001-06-06 18:25 ` Charles Martin
2001-06-06 19:27   ` Michael Hicks
2001-06-06 21:15   ` David Fox
2001-06-07 12:25   ` FabienFleutot
2001-06-08  0:27   ` Miles Egan
2001-06-06 19:36 ` William Chesters
2001-06-06 19:55   ` John Max Skaller
2001-06-06 20:06     ` William Chesters
2001-06-07 16:30       ` John Max Skaller
2001-06-08  0:32   ` Miles Egan
2001-06-08  0:56     ` David Fox
2001-06-07  7:35 ` wester
2001-06-07 17:27   ` John Max Skaller

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='002c01c0ef7f$e154f3e0$5d26883e@baby' \
    --to=jonathan@meanwhile.freeserve.co.uk \
    --cc=caml-list@inria.fr \
    --cc=leary@nwlink.com \
    /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).