From: Michael Vanier <mvanier@bbb.caltech.edu>
To: bcpierce@cis.upenn.edu
Cc: Pierre.Weis@inria.fr, garrigue@kurims.kyoto-u.ac.jp, caml-list@inria.fr
Subject: Re: Newsgroup for Caml?
Date: Thu, 15 Jun 2000 13:36:44 -0700 (PDT) [thread overview]
Message-ID: <20000615203644.711145E468@sith.bbb.caltech.edu> (raw)
In-Reply-To: <2844.961073619@saul.cis.upenn.edu> (bcpierce@saul.cis.upenn.edu)
> Cc: garrigue@kurims.kyoto-u.ac.jp (Jacques Garrigue),
> caml-list@inria.fr
>
> I agree that the volume of traffic on the caml-list is close to
> becoming a problem, but I'm not completely happy with the idea of an
> unmoderated newsgroup: in my experience, they *always* fill up with
> spam, off-topic discussions, and other kinds of garbage. I would
> personally not read such a newsgroup.
As a counter-example, look at comp.lang.python. There is very little spam,
and the quality of postings is extremely high. I suspect that people who
like nice languages like ocaml (and python!) are more likely to be
well-behaved than the average usenet poster :-) Also, I think it's less
intimidating for beginners like myself to post to a newsgroup with a silly
question than to a mailing list. comp.lang.ml has always had a strong SML
bias (due, no doubt, to this mailing list providing an alternative forum),
and a very low volume, perhaps due to the moderation. I would rather see
comp.lang.ml.caml or comp.lang.caml than just redirecting news to
comp.lang.ml; how many of us actually read it? Also, I fear pointless SML
vs. CAML flame wars might develop if all the caml traffic were to go to
c.l.ml.
However, a "caml-announce" mailing list would be a very good thing.
Mike
next prev parent reply other threads:[~2000-06-16 15:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-12 19:05 Daniel de Rauglaudre
2000-06-13 16:53 ` Pierre Weis
2000-06-13 23:18 ` Markus Mottl
2000-06-15 3:07 ` Jacques Garrigue
2000-06-15 11:29 ` Pierre Weis
2000-06-15 12:53 ` Benjamin C. Pierce
2000-06-15 20:36 ` Michael Vanier [this message]
2000-06-15 12:22 ` Markus Mottl
2000-06-16 8:01 ` Sven LUTHER
2000-06-14 8:08 ` Jean-Yves Moyen
2000-06-13 19:16 ` Michael Vanier
2000-06-15 13:47 ` Xavier Leroy
2000-06-16 8:07 ` Niall Dalton
2000-06-16 16:44 ` Daniel de Rauglaudre
2000-06-16 8:32 ` Jacques Garrigue
2000-06-16 11:25 ` Alexander I. Zhezherun
2000-06-13 17:02 Dave Berry
2000-06-14 7:18 ` Sven LUTHER
2000-06-15 9:22 Dave Berry
2000-06-15 12:31 Damien Doligez
2000-06-15 13:32 Dave Berry
2000-06-16 18:41 Brent Fulgham
2000-06-19 10:24 ` Jean-Francois Monin
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=20000615203644.711145E468@sith.bbb.caltech.edu \
--to=mvanier@bbb.caltech.edu \
--cc=Pierre.Weis@inria.fr \
--cc=bcpierce@cis.upenn.edu \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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