From: Brian Hurt <bhurt@spnz.org>
To: Richard Jones <rich@annexia.org>
Cc: ocaml ml <caml-list@inria.fr>
Subject: Re: [Caml-list] Sorted list
Date: Sat, 4 Aug 2007 13:17:57 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0708041258290.9657@localhost> (raw)
In-Reply-To: <20070804162135.GA7370@furbychan.cocan.org>
On Sat, 4 Aug 2007, Richard Jones wrote:
> But what's wrong with extlib? Now I know it's not the "Standard"
> distribution, but that's a mere packaging issue.
Actually, extlib is a wonderfull example of what's wrong with this idea.
I have grown to have major philosophical differences with extlib- despite
the fact that I'm one of the major contributors. For example, I'm much
more fond of functors at this point (and I understand them better) than I
did when I first started contributing. At this point, I also prefer
purely functional data structures as a default, even at a performance
penalty- there are damned few places that need to pure speed that
imperitive data structures give you (there are some, but they're a
distinct minority)- in the vast majority of places, the performance
benefits of impertive data structures are vastly outweighed by the
correctness gaurentees applicative data structures can give you.
Others may disagree (in fact, they do)- that's OK. I do not want to
restart the epic arguments that occurred on the extlib list here on the
main list (please, dear God, no). My point here is that the Ocaml
community is much less in agreement on how these core libraries should
look and act than, say, the C++ or Java communities. Even if we limit
ourselves to, say, the Brian Hurts of past and present, the Brian Hurt of
three years ago would have designed a radically different library than the
Brian Hurt of a year ago, who in turn would have a different view than the
Brian Hurt of today (who is learning, and liking, monads). And God only
knows what nutzoid radical ideas the Brian Hurt of a year from now, or
five years from now, will have.
Brian
next prev parent reply other threads:[~2007-08-04 17:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-04 9:35 tmp123
2007-08-04 10:00 ` [Caml-list] " Jon Harrop
2007-08-04 10:29 ` Philippe Wang
2007-08-04 11:22 ` skaller
2007-08-04 12:23 ` Philippe Wang
2007-08-04 13:39 ` skaller
2007-08-04 14:01 ` Philippe Wang
2007-08-04 14:45 ` skaller
2007-08-04 14:27 ` tmp123
2007-08-04 20:33 ` Christophe TROESTLER
2007-08-04 14:37 ` tmp123
2007-08-04 15:09 ` Brian Hurt
2007-08-04 15:42 ` skaller
2007-08-04 16:21 ` Richard Jones
2007-08-04 17:17 ` Brian Hurt [this message]
2007-08-04 18:24 ` skaller
2007-08-04 17:54 ` skaller
2007-08-04 19:16 ` Richard Jones
2007-08-05 16:22 ` David Allsopp
2007-08-05 16:41 ` Xavier Leroy
2007-08-05 17:01 ` David Allsopp
2007-08-04 17:35 ` Julien Moutinho
2007-08-04 18:04 ` skaller
2007-08-05 1:47 ` Jon Harrop
2007-08-05 11:44 ` Erik de Castro Lopo
2007-08-05 12:03 ` Jacques GARRIGUE
2007-08-05 12:31 ` Erik de Castro Lopo
2007-08-05 13:22 ` Richard Jones
2007-08-05 20:47 ` Erik de Castro Lopo
2007-08-05 13:17 ` Richard Jones
2007-08-05 16:26 ` Xavier Leroy
2007-08-05 23:47 ` skaller
2007-08-04 15:36 ` skaller
2007-08-04 15:17 ` tmp123
2007-08-12 12:05 ` Andrej Bauer
2007-08-04 12:15 ` Brian Hurt
2007-08-04 12:36 ` Brian Hurt
2007-08-04 13:49 ` skaller
2007-08-04 12:16 ` Daniel Bünzli
2007-08-04 12:58 ` Oliver Bandel
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=Pine.LNX.4.64.0708041258290.9657@localhost \
--to=bhurt@spnz.org \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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