Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Reading the article you linked to got me thinking about one of the truly hateful geek tendencies: responding to a problem by proposing a completely different toolset. (Where "toolset" depends on the domain under discussion...)

    For instance, I say: "I've got a working CGI::Application app but am trying to get it to do X and am having problems. Has anyone done this before?" Someone responds, "Well, if you used webapp framework Y you could do it so much easier...."

    ...yeah, and if my aunt had testicles she'd be my uncle. Sure, I'll invest days and days to relearn a whole bunch of configurations, ideologies and quirks just to get back to where I am right now. And spend a few more weeks to rewrite all my applications use this fantastic new framework, a few more to fix all the bugs I introduced. And then in a few months I'll say, "I've got a working Y app but am trying to get it to do X..." and the whole process will start again. Hooray!

    But [google.com]. That's how we wind up changing technologies, isn't it? Otherwise Perl probably never would have replaced the shell/awk/sed/etc. toolset without Randal and Larry enlightening sysadmins on usenet. (Or maybe it would have done so much more slowly.)

    So it certainly has a place, even in public. I guess I just wish people would think about these things before pushing their kool-aid. (Not much of a rant conclusion, eh?)