Code that's too large to post

Greetings noble monks,

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"

Comment on Code that's too large to post

Replies are listed 'Best First'.
Re: Code that's too large to post by Masem (Monsignor) on Mar 30, 2002 at 21:27 UTC
jcwren offers up perlmonk.org (note the lack of plurality) for any monk that wants to host a web page or for testing scripts; more details are available on this page. This is one option for having perl-related code on a perl-related but offsite page. You can also duplicate your code on your website if you have one. ----------------------------------------------------- Dr. Michael K. Neylon - mneylon-pm@masemware.com \|\| "You've left the lens cap of your mind on again, Pinky" - The Brain "I can see my house from here!" It's not what you know, but knowing how to find it if you don't know that's important	[reply]
(dooberwah) Re: Re: Code that's too large to post by dooberwah (Pilgrim) on Mar 30, 2002 at 21:46 UTC
Yes, I actually have an account on jcwren's server. Unfortunately, perlmonk.org could go down just like any other site. The only difference would be that we'd discover it quicker because someone would be bound to report it one Perl Monks. -Ben Jacobs (dooberwah) http://dooberwah.perlmonk.org "one thing i can tell you is you got to be free"	[reply]
(jeffa) Re: Code that's too large to post by jeffa (Bishop) on Mar 30, 2002 at 22:45 UTC
I use my perlmonks.org account to link offsite code, but only to enhance a post, not to act as a substitute for the post. I think you are taking merlyn's reply a bit out of context (and please forgive me if i do the same to you or him). I don't believe he downvoted _JUST_ because the entire code is linked offsite, but ALSO because the code in question is more than likely a reinvention of a wheel that already exists on CPAN. (cough POE) I braved the download (i really hate .zip files - i'm a tar ball kinda guy) and there are 16 different versions of the code. The final version is indeed long (21Kbtyes and 553 lines), but that is not too much for this site to handle ( HTML::Template Tutorial is currently 19KBytes and 525 lines long). Now, if Veachian64 had turned this into a web site that acted as a tutorial for IRC programming (like Ovid did with his online CGI course), then that would be another story (hint hint). Use offsite linking to enhance your content - not to replace it. jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)	[reply]
Re: Code that's too large to post by DaWolf (Curate) on Mar 31, 2002 at 07:22 UTC
Sorry, jeffa, but you're taking a pretty too-much-assumed defense here. You wrote: "I think you are taking merlyn's reply a bit out of context (and please forgive me if i do the same to you or him). I don't believe he downvoted _JUST_ because the entire code is linked offsite, but ALSO because the code in question is more than likely a reinvention of a wheel that already exists on CPAN. (cough POE)" Well, if merlyn downvoted the guy for any other reason he didn't took the time to explain it. I agree that what merlyn did is wrong if the perlmonks site blocked the guy from posting his code because of size. What else he could do? Don't post at all? BTW merlyn's argument is too weak, since we are a community. If for any reason the link dies, just ask the author for a new one. That's why we have the /msg thing on chatter box or even - if you want to keep things simple - a mail link to the author of the post. It is there - the mail link - you know? Regards, Er Galvão Abbott a.k.a. Lobo, DaWolf Webdeveloper	[reply]
(jeffa) 2Re: Code that's too large to post by jeffa (Bishop) on Mar 31, 2002 at 23:26 UTC
"... you're taking a pretty too-much-assumed defense here." Guilty as charged. Sorry if i broke karma. "What else he could do? Don't post at all?" I think posting the final version would have been much more appropriate, then the link would have provided 'extra bonus material' for anyone interested. Add kudos to you DaWolf for bringing up community. jeffa L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)	[reply]
Re: (jeffa) 2Re: Code that's too large to post by agentv (Friar) on Apr 03, 2002 at 01:25 UTC
...I'm strongly behind this position as clarified here. I think posting the final version would have been much more appropriate, then the link would have provided 'extra bonus material' for anyone interested. Certainly a blind policy of downvoting anything that links to an offsite resource would be negative. There are many good reasons that offsite links would be appropriate. It sounds like there might have been some other issues but those seem to have been worked out. Add kudos to you DaWolf for bringing up community. And thanks to all here for demonstrating it. (A revised and clarified position, a new post with the cleaner access to the code, and the general sense that we should do whatever seems most reasonable to us, as long as we're willing to occasionally reconsider our definition of reasonable. I'm in!) ---v	[reply]
Re: Code that's too large to post by Veachian64 (Scribe) on Apr 01, 2002 at 01:01 UTC
Update: Tarred version is now available, link is at node. It's good to know that people are actually looking at my code. =] At jeffa's suggestion, I'll post the latest version of the code at The Veachian IRC Daemon. I opted to put out the other versions so people could see how the code evolved, what things I changed and took out, etc. I'll put up a tarred version later too. I didn't have access to my Linux box at the time, so zip was all I had. Anyway, thanks for the input everyone, it's much appreciated =]	[reply]


good chemistry is complicated, and a little bit messy -LW
	PerlMonks