http://www.perlfoundation.org/perl6/index.cgi
http://www.perlfoundation.org/parrot/index.cgi
Contributions of content are of course always welcome.
Please consider linking to these wikis where appropriate, to help raise
their visibility and utility.
(Also consider dropping a note to perl6-users about major wiki updates of
general interest to Perl 6 test drivers and fans.)
FYI, there's also an official Perl 5 wiki.
http://www.perlfoundation.org/perl5/index.cgi
Best regards,
Conrad Schneiker
Besides, I hope that the language and wiki will be successful enough
that a cgi-based implementation will completely fail to scale to meet
demand. :)
--
Mark J. Reed <mark...@mail.com>
Maybe the site maintainers could add an Apache rewrite rule
so the URLs used by the public will be
http://www.perlfoundation.org/perl6/index.p6
and
http://www.perlfoundation.org/parrot/index.parrot
That would change the perception and we would not need to explain
about mod_perl running the .cgi scripts at the rate 100-200 faster
than good old CGI.
When asked if they really run on Perl 6 and Parrot we could just smile...
Gabor
> Maybe it's just me, but it
> seems like it will just feed the all-too-common perception that Perl
> is for CGI scripts, and "real" web apps need to be written in
> something else (be it Java, PHP, Ruby/Rails, whatever).
Proposed new rule: for every ten contributions to the wiki, you get one
bikeshed mail.
-- c
> Ok, consider me duly chastised. Sorry for the sidetracking.
It's not a *bad* idea, but it's less important in my mind than getting useful
information on the wiki. Anyone who wants to pursue it can do so, but I'd
like to forestall a long digression on the list about it. That's all.
-- c