Re^7: What's wrong with Perl 6?

I agree with Paul's point, and I certainly don't mean to sound like code-writing is the only thing that's valuable in Perl 6. But at this point I also don't see that any amount of public communications is going to do anything useful, especially if it's going to draw Perl 6 developers away from coding.

We can only hold off people with public discussions for so long before they say "I give up on this Perl 6 thing." I feel like anything being done w/Perl 6 that isn't writing code is, at this point, just navel gazing.

xoxo,
Andy

Comment on Re^7: What's wrong with Perl 6?

Replies are listed 'Best First'.
Re^8: What's wrong with Perl 6? by chromatic (Archbishop) on May 15, 2007 at 05:27 UTC
I feel like anything being done w/Perl 6 that isn't writing code is, at this point, just navel gazing. I agree, if you replace "writing code" with "contributing". There are plenty of tasks that will help Perl 6 arrive that aren't explicitly writing code. Helping write tests--or especially introductory documentation for new users and contributors--is at least as important as writing code right now.	[reply]
Re^9: What's wrong with Perl 6? by petdance (Parson) on May 15, 2007 at 13:58 UTC
I agree, if you replace "writing code" with "contributing". Let's just say "building something." xoxo, Andy	[reply]
Re^10: What's wrong with Perl 6? by TimToady (Parson) on May 15, 2007 at 16:07 UTC
Let's just say "building something." I like that. Now we just need to define "something" to include healthy communities, and I can die happy. `:-)`	[reply]