|XP is just a number|
Death and Return of TIMTOWTDIby dakedesu (Scribe)
|on Jun 02, 2004 at 01:45 UTC||Need Help??|
Sorry for the bump if there is any, this update on this thread is merely for if it shows up in the search engines
Update: I would like to apologise for this thread. I'll keep it the same with this prefixed message. I was merely getting a tad bit annoyed with CPAN modules that refused to install because one out of like 99 tests failled, or stuff that I really did not care about. However, that is an excuse. Looking over this thread again, I realise I was unwittingly a troll. I sparked a holy war, and ended up getting burned. Yes, most of the discussion was civil, however, I handled myself horrible in this thread.
Please accept my apologies. Here is the thread, unchanged, not so much for the point of replying to, but more to show up in the search engine, should the need for a thread like this arise again.
A lot of questions get answered with, "hey, just download the version on CPAN."
Yes, in a lot of instances, that is the best idea, but one has to wonder about how much things are being hindered by that answer. A lot of people on this site probably could make something equivilent, if not just slightly a little less well crafted.
Onlamp has put up articles on how people can help the perl projects, and the idea of redundant code might be a good thing. Mostly as that redundant code might contain slight twists and turns that the code already there does not have. Slight eccentricities that might make the redundant code somewhat more well liked.
Similar, kind-of to why there are several Linux Distros
If somebody thinks they want to try something that is already on CPAN, why not let them? If they do, they might get a better understanding of how the code on CPAN works. Even possibly might be able to add that knowledge to their current projects.
This is not a concept limited to this community. Several other perl communities are just listing off 'Look on CPAN it is there.' Yes, most problems have already coded solutions, but then, that was in the 1970s. Does that mean we simply should use 1970s software? This seems to infecting perl communities, the CPAN monolith.
Currently, I am working on several things that I know have definitely got to be somewhere on CPAN. Why? To learn how to code that sort of thing. Maybe, if the results of the labour to make that code are comparable to that on CPAN, maybe CPAN might get a new entry. If anything, the person coding the redundant code will learn something (Hopefully).
Choice is good, and I would prefer it if the first answer was not "look on CPAN, and don't attempt to try yourself." Not that this concept might hold any relevance here. Why has TIMTOWTDI died?
Update: Sorry for the lack of replies, there were issues with how I was connecting to the internet. I would also like to apologise for the spawned off discussions in tangents.I will try to get to the replies
-- Jamie Payne