Some people (I for one) like to learn how things work instead of using a module to do the work for them (Others I can't vouch for :P). I'm currently writing an IRC bot in perl and I *could* have used Net::IRC but I wanted to be able to write my own code and my own functions and frankly, I just wanted to learn how IRC worked on a client to server basis (After reading rfc2812). Not saying using modules is bad, but some people might like to learn how stuff works before having a module do it for them.
Re: No excuses about not using CGI.pm
Replies are listed 'Best First'.
So, is this an excuse to not use CGI.pm? No, it is not.
Just because one uses a module does not necessarily mean
that one does not understand how 'things' work - period.
One uses a module because they want to get stuff done.
I find nothing wrong with the desire to learn things, i
find nothing wrong with reinventing wheels to further your
own education. What i do find wrong is the attitude that
using CPAN modules is a 'cop-out'.
Here is a scenario, you have 1 day to write an IRC bot.
What do you do? You use Net::IRC and keep your job. That's
what we are talking about here.
"Some people ... like to learn how things work instead
of using a module to do the work for them..."
No one said you can't do both, some people like
to use the module and THEN figure out how they work, if
only because the person who wrote that module has more
experience and can offer a tried and tested road to
explore. perldoc -m is your friend. :)