caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Damien Guichard" <alphablock@wanadoo.fr>
To: "Matt Gushee" <mgushee@havenrock.com>, <caml-list@inria.fr>
Subject: Re: [Caml-list] The Caml morale crasher #1
Date: Wed, 7 Sep 2005 20:06:51 +0200	[thread overview]
Message-ID: <005801c5b3d6$eeff2900$62310c50@oemcomputer> (raw)
In-Reply-To: <431ED5FD.5050100@havenrock.com>


Hi,

Thanks for encouragements.

Indeed OCaml is all about lambdas, any OCaml function is a named-lambda.
OCaml without lambda-calculus is just impossible.
Another adjective for OCaml was "esoteric" and another about Milner type
system was "over the top feature".

I think the only possible answer is to deliver, the functionality overcomes
the resistance.
The first language that delivers has great chances to become the standard.
People that fear OCaml can deliver faster just prove OCaml is better.

- damien



----- Original Message -----
From: "Matt Gushee" <mgushee@havenrock.com>
To: <caml-list@inria.fr>
Sent: Wednesday, September 07, 2005 1:58 PM
Subject: Re: [Caml-list] The Caml morale crasher #1


> Damien Guichard wrote:
>
> > http://www.bytesmiths.com/Publications/9701ArchitectsVersusCoders.html
>
> Unfortunately, I couldn't connect with this site, but I will venture a
> comment anyway. Since I know nothing about your project, I can only
> respond in the most general terms.
>
> > When annoucing an OCaml project on a public forum i have been advised to
> > renunce lambdas because it would impede translation to "a less obscure,
> > more popular language".
>
> And I imagine the same people who said that would also advise you not to
> use higher-order functions and variant types. Just sacrifice some of
> OCaml's most powerful features for the sake of compatibility ... or
> perhaps we should say (social) conformity. It might be a useful tactic
> in some specific cases, but as a general principle, if you're going to
> do that, why bother with OCaml at all?
>
> Let's assume you had good reasons for choosing OCaml (people who use
> non-mainstream languages usually do). The question then is whether there
> is any practical need for the members of that forum to accept your
> methods. If so, then try again to make your case ... I'm sure there are
> people here who can suggest some "talking points." Otherwise, well,
> innovation has always met with resistance, and probably always will.
> Have confidence in your choices and forge ahead. Or give up. It's your
> choice.
>
> Best of luck with your project.
>
> --
> Matt Gushee
> Englewood, CO, USA
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>



  parent reply	other threads:[~2005-09-07 18:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-01 16:32 Damien Guichard
2005-09-03  6:06 ` Erik de Castro Lopo
2005-09-07 11:58 ` Matt Gushee
2005-09-07 18:06   ` Damien Guichard
2005-09-07 18:06   ` Damien Guichard [this message]
2005-09-09 22:17   ` Stefan Monnier
2005-09-08 12:46 ` [Caml-list] " Florian Weimer
2005-09-08 12:55 yoann padioleau
2005-09-08 16:35 ` skaller
2005-09-08 16:44 ` David Brown
2005-09-08 17:14   ` Florian Weimer

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='005801c5b3d6$eeff2900$62310c50@oemcomputer' \
    --to=alphablock@wanadoo.fr \
    --cc=caml-list@inria.fr \
    --cc=mgushee@havenrock.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).