in reply to Modules that do Less
I do agree that modules sometimes grow larger than is healthy for them. There's always the temptation to add that one additional feature-- it'd be cool, and wouldn't hurt anything, one thinks to oneself. Following this path, one can end up with a module so bloated it's difficult to understand. A module should do one thing and do it well.
Even so, I think that CGI doesn't fall into that category. Even if it has some features that you don't use, these functions aren't hurting you because until you use them they're not even compiled.
From Lincoln Stein's web site:
Ordinarily CGI.pm autoloads most of its functions on an as-needed basis. This speeds up the loading time by deferring the compilation phase.
In other words, there's rarely any reason to worry about loading CGI.pm. It loads in only the parts that you use.