I had a response all typed up, but I erased it. I just want to learn enough so I can start coding, and these pod conversations are just getting in my way, and I don't want to waste the Parrot communities time or bandwidth with my trivial issues. Your time is much more valuable getting perl6 up and running than defending pod.
I think the problem is that this community is a hard-core perl community, and as such pod is second nature. I imagine that when you look at a text file that contains pod you don't see all the blank lines, equal signs, or html looking things that I see, you honestly see a well formatted document. I have not reached that level of podness. It would be like me getting frustrated at the Germans because they write their source code comments in German (no offense to the Germans). Duh... The name of the mailing list is perl6-internals, and this is first and foremost the Perl6 interpreter. I got caught up in the multi-language aspect of Parrot and I guess I was pushing that point. I am sure that if this group consisted of primarily java programmers there would be javadocs all over the place. I hope that the first draft of my "getting started" guide will be ready on Tuesday. I hope that there will be other newbies out there that can give me their feedback on the guide. Sorry for all the bandwidth I chewed up, but at least I got some people thinking about documentation. If there are any people out there that want to get involved in parrot but don't know how or feel intimidated to post to the group, just send an email to me with your questions or comments and I will try to get them addressed in the guide. Thanks, Erik
