RFC: Community Education Page

2006-05-07 Thread David K Storrs
Hmmm...This doesn't seem to have particularly grabbed the popular imagination among the Perl6 crowd. Let me ask something a little more concrete and see if that gets us to ignition, otherwise it's probably not feasible. Assume that I'm going to create, host, and maintain a small website

RFC: Community education page

2006-05-04 Thread David K Storrs
I was chatting with a P6 person the other day (who can remain nameless unless he chooses to identify himself). He made the following observation: Every time we're lambasted for how long Perl 6 is taking I remind myself that Short Term Thinking is the norm now. I think there are a couple

Re: RFC: Community education page

2006-05-04 Thread David K Storrs
On May 4, 2006, at 10:59 AM, [EMAIL PROTECTED] wrote: On Thu, May 04, 2006 at 10:44:29AM -0400, David K Storrs wrote: Also, the page should talk about why it is difficult to do what is being done. Ask the reader questions: You want to support continuations / have coroutines / embedd yacc

Re: A proposition for streamlining Perl 6 development

2006-02-07 Thread David K Storrs
On Feb 7, 2006, at 5:33 PM, Allison Randal wrote: Parrot, on the other hand, has noticeably gained momentum the past 6 months or so. AFAICT, this is largely due to the fact that we're close enough to finished that we can see the light at the end of the tunnel, and because Pugs reminded us

Re: A proposition for streamlining Perl 6 development

2006-02-07 Thread David K Storrs
On Feb 7, 2006, at 6:51 PM, David K Storrs wrote: I'd say that qualifies as light at the end of the tunnel indeed! Forgot to say...all of this was was predicated on the idea that the code can't really be written until the spec is done. Once the spec is complete (even if not totally

Re: split on empty string

2006-01-18 Thread David K Storrs
On Jan 18, 2006, at 1:18 AM, Jonathan Scott Duff wrote: On Tue, Jan 17, 2006 at 12:35:57PM -0500, Mark Reed wrote: On 2006-01-17 12:24 PM, Gaal Yahas [EMAIL PROTECTED] wrote: [split on empty string] doesn's seem to be specced yet. I would prefer the current pugs behavior; it's consistent