caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: leary@nwlink.com
To: Jonathan Coupe <jonathan@meanwhile.freeserve.co.uk>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml complexity
Date: Fri, 8 Jun 2001 15:46:23 -0700	[thread overview]
Message-ID: <20010608154623.A15375@jean> (raw)
In-Reply-To: <003601c0f016$7ac12940$a00bfea9@baby>; from jonathan@meanwhile.freeserve.co.uk on Fri, Jun 08, 2001 at 01:27:33PM +0100

On Fri, Jun 08, 2001 at 01:27:33PM +0100, Jonathan Coupe wrote:
> If this was the decisive issue, people would just use C++ with GC.
<snip>
> Finally, you don't really know the cost/benefit ratio for a technology until
> the day you manage to ship. You certainly won't be able to convince any
> sceptical colleagues or managers of it, and that's what governs the adoption
> rate for new technologies.

No one factor is decisive, of course, else people would be using OCaml
(more) already.  But it looks like you're saying that adoption is governed
by people who can't be convinced to adopt unless they've shipped something
using the untried technology.  Let's just give up now, ok? ;)  Seriously,
IMHO, there ought to be a compelling case for OCaml that can be made on
paper, and supplemented with some relatively small projects (examples?
exercises for the reader?) which demonstrate the value.

> Many programmers don't know what fp is;
> more are positively allergic to it because of bad academic intoductions.

One of my main points: there is a lack of good tutorials aimed at people
who don't give a rip about the theory and lingo of language design, beyond
knowing the basics: http://caml.inria.fr/FAQ/general-eng.html .

> It's not easy conveying the benefits of the OCaml type system to an
> industrial C programmer either.

Really?  I'm a pretty lightweight programmer (Perl and a bit of C) by
comparison, and I didn't have trouble grasping the benefits.

> Claiming benefit here is easy. Persuading
> someone else that it exists requires real intellectual effort on your part
> and theirs. I don't think anyone could this better than Mark Dominus did
> with his article, which is probably a good hour's read.

I guess you mean this?: http://perl.plover.com/yak/typing/typing.html

> If the benefits
> Ocaml provides here were obvious, I don't think you'd have written that
> trying to understand the type system makes your eyes "glaze over."

My apologies for being unclear; it's just that I'm... unclear.  Hmmm, let
me put it this way: I've read dozens of chapters in books on ML and OCaml,
yet I can't even figure out half the *questions* that are asked on this
list.  Some of that is surely that I haven't read far enough to have
covered some of the particulars, but a good part of that is the language
(of programming languages) that is quite new to me.  I guess what I'm after
is: Where is the HHGT deciphering FP discussions?  (see my reply to the
HHGT Typing)

> Perl is widely used. Ocaml, Scheme, CLOS and Smalltalk aren't, despite being
> better languages. The reason why is partly that Perl is a more marketable
> language - it fits into niches where new tools can spread more easily, and
> because its benefits are easily communicated, potential users can easily be
> persuaded to try it out.

Scheme and CLOS aren't more widely used because people don't like the
parentheses.  And a good number of the most visible people who advocate
them are rabid emacs zealots -- talk about losing half your audience at the
start.

I went to the GNU Smalltalk site -- where a lot of people are going to go
first, if they're curious.  No good tutorials that I could see, the manual
looked pretty unfriendly -- what I got a chance to see of it.  The html
manual is on an ftp server that allows 10 users, so people might not be
able to read up on it enough to want to download.  I wasn't.  There's also
no evidence of *why* I should want to learn and use Smalltalk.  And anyway,
I'm not a big fan of using OOP (and certainly not for everything), as many
people aren't.  OCaml doesn't seem to force it on the user.  That's a
selling point.

Anyway, you don't think the great numbers of Free Software and Open Source
hackers can get excited about FP and OCaml?  I think they can.  I think the
benefits are easily communicated ( see again:
http://caml.inria.fr/FAQ/general-eng.html )  Remember, these are the people
who enjoy the Unix command line; who have made PHP and Python into viable
solutions in the face of Perl, C++, and Java; who actually do use Scheme
and CLOS and Guile and Emacs Lisp.  Look at the language shootout page.
OCaml is #2 and #4.  Yeah, yeah, speed isn't everything, but it *is* a
selling point for geeks, esp. when OCaml is so far ahead of languages like
Perl, Python, Ruby, Emacs Lisp, TCL and PHP; all of which are far "cooler"
right now.  And now there is PCRE-OCaml; a gold-plated opportunity to
interest some Perl folks in looking more closely at OCaml.

-------------------
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


  parent reply	other threads:[~2001-06-08 22:46 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
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 [this message]
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=20010608154623.A15375@jean \
    --to=leary@nwlink.com \
    --cc=caml-list@inria.fr \
    --cc=jonathan@meanwhile.freeserve.co.uk \
    /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).