NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
books.perl.org (Score:2, Informative)
Re:books.perl.org (Score:1)
I do recall that.
I'm kind of split between wanting it here on use perl, which is sort of an existing community hub, or on books.perl.org, because it deserves its own site. For various reasons which may become apparent later, I'm leaning towards the latter at the moment.
-dave
Re:books.perl.org (Score:1)
Re:books.perl.org (Score:1)
Reply to This
Parent
Re:books.perl.org (Score:1)
Re:books.perl.org (Score:1)
(I'm joking, for those who aren't sure)
More seriously, I was thinking generally about whether we'd want to require a 100% overlap between having admin powers for book stuff and admin powers for use Perl in general. I, being a paranoid sort, tend to favor isol
Re:books.perl.org (Score:1)
Re:books.perl.org (Score:1)
Re:books.perl.org (Score:1)
Yes, but that is a reflection of your limited knowledge, not of Slash. :-) Slash is completely flexible in such matters.
there is also a very quiet companion email list for this which might be a better forum than use.perl
Why?
Re:books.perl.org (Score:1)
Re:books.perl.org (Score:1)
Slash is a general web application server. It can be anything you want it to be. pudge.net has a photo gallery and football picking. It is quite simple to add a search interface like that to Slash, you just write a simple plugin. Slash is actually very good at that kind of thing.
as for why a mailing list is better that a web forum, i just can't answer that. it just is. :) you obviously have a biased view towards use.perl. :)