i like CGI programming. i find the many projects i can do on the web interesting. but i don't use perl just for CGI.

examples of my CGI projects: a somewhat-well-scaling flatfile message board, a simple cgi web proxy, a somewhat flatfile search engine (faster than hash dbs), and other things ive forgotten about.

examples of my non-CGI projects: a dual generation MP3 streamer, a small web server, a simple Ncurses shell (yes for logging into), a variant on one-time pad encryption, a powerful qmail masquerading filter, an AOL Instant Messenger bot, a log parser/alert system, a user registration/login/authentication database, and more things ive never gotten past alpha.

as you can see, i don't just do CGI. i wish i could stick to one project and make it really good, but i have so many ideas i have to make a new project every week or two. damn that ADHD! what makes things worse is now i've gotten into gaming, so now i have 5 things that occupy my time: studying for computer certifications, trying to get a job, playing multiplayer FPS's, programming, and trying to maintain a social life before i go insane. plus i administrate a 2600 meeting, do small part-time work as a consultant, run a server at a lan party, and now i have to start working out because none of these things involve aerobic excercise.

ok so that went off in a different direction. what im saying is that perl's strength isn't CGI, it's the code itself; how you use it determines how it'll be seen by others. i can't wait for the first linux perl kernel module }:>