>> In the past couple of years we've seen several sub-projects pop-up
>> and subsequently fizzle out (maybe due to Parrot slow
>> progress or maybe due to lack of critical mass).

>> I propose creating 'parrot-compilers' as a general
>> purpose list for any and all language development

> ...

> So I'll be one of the few nay-sayers. I'm not definitely against it, but
> here are two counter-arguments:

> 1) It's likely that we've seen very little traffic (at least recently)
> about language development because either as you said Parrot isn't quite
> ready, or because of lack of interest. If so, a new list won't help.

> 2) Forking a list almost always leads to an increase of messages of the
> form "you should be asking this on the other list...", and/or of
> cross-posting, neither of which is very interesting to deal with. I'm of
> the opinion that unless traffic is unmanageable, fewer lists is better.
> So I think a fair question to ask is: How many people currently
> subscribed to this list would not subscribe to both? For those who
> subscribe to both, splitting wouldn't be an improvement.

> I doubt that the name of the current list is actually a big problem,
> because no matter what the name is, you'll find out about the list by
> reading a blurb about it somewhere, which will explain why it's named
> this way. Those who are off-put because they hate Perl are going to
> probably not like the content of the discussion either, because it will
> constantly come up.

> Again, I'm not dead-set against it--I just don't think it would improve
> anything.

> JEff