From: Ville-Pertti Keinonen <will@exomi.com>
To: Robert Morelli <morelli@cs.utah.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Some Clarifications
Date: Mon, 25 Jul 2005 10:23:30 +0300 [thread overview]
Message-ID: <42E49372.3040700@exomi.com> (raw)
In-Reply-To: <42E2DB1E.2010508@cs.utah.edu>
Robert Morelli wrote:
> To be entirely frank, I am put off by the style of your comments.
My annoyance with regard to your (largely unsubstantiated) points was
probably apparent in my style.
> If you disagree with my answer to the subject of this discussion,
> you should point the original poster to what you think is a
> discussion of large scale functional design, or present your own
> explanation for why it doesn't exist. I would be genuinely interested
What is large-scale OO design, then?
Most of the methodologies (abstraction, layering, tools such as UML) I'm
aware of translate more-or-less directly to (stateful) FP in general,
and OCaml in particular as it provides OO abstraction as well as functional.
> in what you have to say. But instead, you have chosen to veer off into
> rhetoric, advocacy, and ad hominem distractions. I am puzzled by your
First of all, I apologize if my points appeared to be ad hominem
attacks, they were not intended as such. I'm still curious as to your
amounts of relative experience in different languages and paradigms -
that was a question, not an attack - and I may have veered too far into
speculation about common reasons why people may draw the kinds of
conclusions you seemed to be implying in your posts. It was
speculation, not assertion.
> citing points about Erlang and concurrent variants of ML that sound
> superficially to be relevant, but which have no real bearing on
> anything I said. I disagree with the frequent use of this mailing list
You were citing increased need for parallelism as a reason for FP to
become less relevant in the future; I think that specific examples of
combining concurrency and functional approaches are valid counterexamples.
Please be specific as to why they aren't relevant.
> to irrationally promote OCaml as a superior language to Java. It is not
What criterion are used to evaluate superiority are of course extremely
subjective. Personally I consider expressiveness to be very important.
Do you disagree that OCaml is more expressive (i.e. there are more
things that can be concisely expressed in OCaml but not in Java than
vice versa)?
If there are things that you find are simple to do in Java (preferably
as a language rather than through its library collection) but not in
OCaml, I'd very much like specific examples.
It's entirely valid to disagree on the importance of expressiveness, or
whether providing a variety of tools for abstraction vs. concentrating
on a single paradigm is better.
next prev parent reply other threads:[~2005-07-25 7:23 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 18:00 (Mostly) Functional Design? Kyle Consalus
2005-07-18 7:59 ` [Caml-list] " Robert Morelli
2005-07-18 9:22 ` Alex Baretta
[not found] ` <42DB78D3.7010401@andrej.com>
2005-07-18 10:01 ` Alex Baretta
2005-07-18 18:15 ` Robert Morelli
2005-07-18 18:45 ` Alex Baretta
2005-07-18 18:56 ` padiolea
2005-07-18 19:19 ` Jon Harrop
2005-07-18 19:38 ` Jon Harrop
2005-07-18 21:27 ` skaller
2005-07-18 21:55 ` Alwyn Goodloe
2005-07-18 22:16 ` Paul Snively
2005-07-19 0:45 ` Jonathan Bryant
2005-07-18 21:37 ` skaller
2005-07-18 22:00 ` Kenneth Oksanen
2005-07-18 9:29 ` Mark Meyers
2005-07-18 9:56 ` Large scale and FP (was: Re: [Caml-list] (Mostly) Functional Design?) David MENTRE
2005-07-18 18:11 ` Large scale and FP Robert Morelli
2005-07-18 14:08 ` [Caml-list] (Mostly) Functional Design? james woodyatt
2005-07-18 16:37 ` Alwyn Goodloe
2005-07-18 14:21 ` alphablock
2005-07-18 15:26 ` Alex Baretta
2005-07-18 15:38 ` alphablock
2005-07-18 17:17 ` Doug Kirk
2005-07-18 18:14 ` Alex Baretta
2005-07-19 7:42 ` james woodyatt
2005-07-19 9:35 ` Robert Morelli
2005-07-19 16:53 ` james woodyatt
2005-07-19 17:13 ` Paul Snively
2005-07-19 23:58 ` Jon Harrop
2005-07-20 0:29 ` Paul Snively
2005-07-18 18:23 ` padiolea
2005-07-18 19:45 ` Gerd Stolpmann
2005-07-18 22:16 ` skaller
2005-07-19 0:48 ` Chris Campbell
2005-07-19 20:14 ` Some Clarifications Robert Morelli
2005-07-20 6:18 ` [Caml-list] " Ville-Pertti Keinonen
2005-07-24 0:04 ` Robert Morelli
2005-07-24 2:30 ` Paul Snively
2005-07-24 7:37 ` Alex Baretta
2005-07-24 8:08 ` Robert Morelli
2005-07-24 12:23 ` David Teller
2005-07-24 18:29 ` skaller
2005-07-24 18:51 ` Paul Snively
2005-07-24 12:42 ` Gerd Stolpmann
2005-07-25 7:23 ` Ville-Pertti Keinonen [this message]
2005-07-20 7:34 ` David MENTRE
2005-07-27 15:37 ` Robert Morelli
2005-07-27 20:33 ` skaller
2005-07-27 23:48 ` Paul Snively
2005-07-20 16:28 ` Damien Doligez
2005-07-24 14:51 ` Robert Morelli
2005-07-24 16:11 ` David MENTRE
2005-07-25 12:21 ` Damien Doligez
2005-07-25 15:47 ` Richard Jones
2005-07-22 5:18 ` [Caml-list] (Mostly) Functional Design? Marius Nita
2005-07-27 9:38 [Caml-list] Some Clarifications Don Syme
2005-07-27 10:58 ` Jon Harrop
2005-07-27 11:55 ` Robert Roessler
2005-07-27 14:01 ` Richard Jones
2005-07-28 0:29 ` Robert Roessler
2005-07-27 18:42 ` skaller
2005-07-27 13:36 ` David Thomas
2005-07-27 13:53 ` Ville-Pertti Keinonen
2005-07-27 16:23 ` james woodyatt
2005-07-27 14:32 David Thomas
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=42E49372.3040700@exomi.com \
--to=will@exomi.com \
--cc=caml-list@yquem.inria.fr \
--cc=morelli@cs.utah.edu \
/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