Today, while I was browsing through the Newest Nodes, I came upon The Veachian IRC Daemon. The author of the post had written up a description for the Code section and then given a link to his program, because it was too large to post on the Perl Monks website. The honorable merlyn replied to the post and said that he had downvoted it, because it linked offsite. His reasoning was that the site might not be around the next time somebody trys to access the code.
This brought me to wondering about what we can possibly do with code that's too large to post on Perl Monks, but would benifit from the wisdom of the monks. My first thought was to have some space on a ftp server set up for each user. Since the text boxes are probably 64k each user wouldn't need more than half or quarter of a meg, since they could zip their slightly longer works. This would be small enough that it would be hard to abuse (certainly it could be abused though, which is a bit of a problem), since it would be too small for users to upload their MP3 or image collections, but large enough to be useful for code.
On a somewhat related note: the PerlMonks modules 2.0, which have been several useful Perl Monks related utilities, are stored offsite and nobody has seemed to complain about them yet. I'd love to hear what you have to say about the situation. Thanks for lending your ears (or eyes).
-Ben Jacobs (dooberwah)
http://dooberwah.perlmonk.org
"one thing i can tell you is you got to be free"
In reply to Code that's too large to post by dooberwah
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |