From: Kenneth Knowles <kknowles@berkeley.edu>
To: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] suggestion: do not link to www.ocaml.org
Date: Tue, 13 Apr 2004 23:32:14 -0700 [thread overview]
Message-ID: <20040414063214.GA25779@tallman.kefka.frap.net> (raw)
In-Reply-To: <OOEALCJCKEBJBIJHCNJDEEPCHAAB.vanevery@indiegamedesign.com>
On Tue, Apr 13, 2004 at 11:26:26PM -0700, Brandon J. Van Every wrote:
> I suppose I should have said 'many of the features'. I would note that
> industry cares the least about advanced type safety. C# .NET Managed
> Code suffices for now.
I certainly agree that the industry doesn't seem to care about safety. And
their products reflect it, including my own. (Don't tell my boss I said that
:-)
For me, the type safety and extremely powerful data structures and syntax of
OCaml are why I don't use Scheme, and so I take them as fairly defining traits.
Haskell is the only other major player in my book.
C#? I do like it better than Java, and I'm sure it will spread, but anything
without first-class functions (delegates are close, but syntactic abominations -
anonymous inner classes are even more awful) and parametric polymorphism is like
working in the stone age - its not like ML is new.
Kenn
> OCaml seems to offer a combination that other languages lack in part:
> 1) garbage collected
> 2) performance. Lotsa languages can't manage 1 + 2!
> 3) native compiled, byte compiled, or scripted
> 4) type safety
> 5) high level language primitives
> 6) functional or imperative
>
>
> Cheers, www.indiegamedesign.com
> Brandon Van Every Seattle, WA
>
> Taking risk where others will not.
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.643 / Virus Database: 411 - Release Date: 3/25/2004
>
> -------------------
> To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
> Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-04-14 6:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 22:27 Henri DF
2004-04-13 22:43 ` [Caml-list] " Alan Post
2004-04-13 23:01 ` Henri DF
2004-04-13 23:29 ` Christophe TROESTLER
2004-04-13 22:58 ` [Caml-list] " Zed A. Shaw
2004-04-13 23:25 ` Brandon J. Van Every
2004-04-14 1:12 ` John Goerzen
2004-04-14 4:32 ` Brandon J. Van Every
2004-04-14 15:14 ` John Goerzen
2004-04-14 16:28 ` Matt Gushee
2004-04-14 18:16 ` Brandon J. Van Every
2004-04-14 18:36 ` John Goerzen
2004-04-14 5:34 ` Kenneth Knowles
2004-04-14 6:26 ` Brandon J. Van Every
2004-04-14 6:32 ` Kenneth Knowles [this message]
[not found] ` <20040414070841.GA6062@roke.freak>
2004-04-14 7:32 ` Kenneth Knowles
2004-04-14 11:12 ` skaller
2004-04-14 16:01 ` Kenneth Knowles
2004-04-15 0:32 ` skaller
2004-04-15 5:37 ` Kenneth Knowles
2004-04-13 23:38 ` Karl Zilles
2004-04-13 23:00 ` Christophe TROESTLER
2004-04-14 15:17 ` Richard Jones
2004-04-14 19:05 ` Xavier Leroy
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=20040414063214.GA25779@tallman.kefka.frap.net \
--to=kknowles@berkeley.edu \
--cc=caml-list@inria.fr \
--cc=vanevery@indiegamedesign.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).