caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: <caml-list@inria.fr>
Subject: RE: [Caml-list] suggestion: do not link to www.ocaml.org
Date: Tue, 13 Apr 2004 16:25:45 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDAEOMHAAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <E1BDWqw-0007Xx-00@mail.zedshaw.com>

Zed A. Shaw
>
> You know, as kind of an outsider, I didn't know there was any
> other site for ocaml.

As one recently interested in OCaml, I concur.  It took me awhile to
find caml.inria.fr and to realize that it was in fact the canonical
site.  From a marketing perspective, the ICFP and the Language Shootouts
are the reasons I became interested in OCaml, there are no other
reasons.  A number of other languages have the features, and some have
much better libraries, packages, and industrial provenness.  What OCaml
apparently has is performance.

The only thing I intensely dislike about the www.ocaml.org website is
the slogan, "The programming tool of choice for discriminating hackers."
This suggests that OCaml is a toy, used by exploratory geeks who don't
know the value of a dollar.  I prefer INRIA's utter blandness to
ocaml.org's championing of the hacker geek ethic.

Don't get me started on the Python Software Foundation's utter inability
to market anything.


Cheers,                     www.indiegamedesign.com
Brandon Van Every           Seattle, WA

"The pioneer is the one with the arrows in his back."
                          - anonymous entrepreneur



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


  reply	other threads:[~2004-04-14  0:02 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 [this message]
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
     [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=OOEALCJCKEBJBIJHCNJDAEOMHAAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --cc=caml-list@inria.fr \
    /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).