"The right way" is the easiest way for me. I don't wanna learn the inner workings of HTTP or other very complicated protocols, just so I can serve up some images and stuff.

Learning to use modules is easier than learning complicated crap.

Real problems or not, you do things your way, and others'll do it theirs, regardless.

Looking it over, I got to thinking about some of the people who wander in here with real problems to solve. We usually advise them to use strict, use CGI, and reuse some set of modules from CPAN.

This website is about learning perl, and while re-inventing wheels is fun and part of learning perl, why would you want to re-invent a wheel when you don't know how to use an existing one.

Why would you want to help some poor sap DEBUG broken CGI parsing code?

When is the last time you heard someone say "Help, I need to write a Win32 GUI program, but I can't use MFC of any other pre-written libraries for building GUI's, please help, this is a real world problem!!!!!!!!"

When is the last time you heard someone say "Help, I need to write an assembler program to draw a nice GUI but I can't use any pre-written libraries. Please help this is a real world problem!!!!!"?

Every time I hear "can't use this/or/that module", I think to myself, "well, then go elsewhere for help".

____________________________________________________
** The Third rule of perl club is a statement of fact: pod is sexy.