caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Martin Jambon <martin.jambon@ens-lyon.org>
To: Amir Chaudhry <amc79@cam.ac.uk>
Cc: Malcolm Matalka <mmatalka@gmail.com>,
	 Anil Madhavapeddy <anil@recoil.org>,
	caml-list@inria.fr, Gerd Stolpmann <info@gerd-stolpmann.de>
Subject: Re: [Caml-list] OUD2013 part of CUFP?
Date: Wed, 03 Apr 2013 11:02:31 -0700	[thread overview]
Message-ID: <515C6EB7.7010109@ens-lyon.org> (raw)
In-Reply-To: <C39F1C63-57C5-490E-A17C-4191E85DADB2@cam.ac.uk>

On Wed 03 Apr 2013 10:32:08 AM PDT, Amir Chaudhry wrote:
>
> On 3 Apr 2013, at 17:54, Gerd Stolpmann <info@gerd-stolpmann.de> wrote:
>
>> Am 03.04.2013 18:39:17 schrieb(en) Malcolm Matalka:
>>> OUD was part of CUFP last year, which is the Commercial part of ICFP. I
>>> did not attend ICFP but just CUFP, and didn't find OUD or CUFP too
>>> academic.  Did you?
>>
>> Can't tell about last year, but I visited both CUFP and OUD twice (independently), and it was ok (well, I gave talks on OUD). But this is not my point - I'm more worried about the audience the event attracts, and also about the character in total. I mean it's a difference whether you have an event of its own (even if small) or if it is part of a larger conference, where you certainly also have visitors just seeking entertainment for a bridge day.
>
> The audience that attends depends on how the event is marketed.  That includes people on this list spreading the word to other commercial users of FP, irrespective of where the event is held.  Apart from a comment about academic ritual, you haven't clarified what the problem really is.  In my view, if the events are described properly and word is spread widely, then anyone who shows up *is* the intended audience.  I personally don't know anyone (academic or otherwise) who'd spend a bridge day by going to events they're not interested in (as opposed to, say, doing some tourist stuff).

"Spreading the word widely" doesn't happen like that - it's the core of 
the problem.

In thought the goal was to raise awareness among professional software 
developers who might consider trying some more "functional" approaches 
to programming.
Pardon my cynicism, but this is different from a meeting whose goal is 
to show academics that their pet language was used by that one person 
in that big company and then pat each other on the back.


Martin


  reply	other threads:[~2013-04-03 18:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03  8:24 Malcolm Matalka
2013-04-03 11:22 ` Anil Madhavapeddy
2013-04-03 13:10   ` AW: " Gerd Stolpmann
2013-04-03 13:41     ` Anil Madhavapeddy
2013-04-03 15:42       ` AW: " Gerd Stolpmann
2013-04-03 16:39         ` Malcolm Matalka
2013-04-03 16:54           ` AW: " Gerd Stolpmann
2013-04-03 17:32             ` Amir Chaudhry
2013-04-03 18:02               ` Martin Jambon [this message]
2013-04-03 18:33                 ` Anil Madhavapeddy
2013-04-03 19:16                   ` Malcolm Matalka
2013-04-03 20:01                   ` AW: " Gerd Stolpmann
2013-04-03 21:21                     ` Gabriel Scherer
2013-04-03 21:45                       ` AW: " Gerd Stolpmann
2013-04-04  7:57                         ` Esther Baruk
2013-04-03 17:08           ` Anil Madhavapeddy
2013-04-03 14:18     ` Ashish Agarwal

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=515C6EB7.7010109@ens-lyon.org \
    --to=martin.jambon@ens-lyon.org \
    --cc=amc79@cam.ac.uk \
    --cc=anil@recoil.org \
    --cc=caml-list@inria.fr \
    --cc=info@gerd-stolpmann.de \
    --cc=mmatalka@gmail.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).