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
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
well said (Score:1)
I think there is a sweet spot if you are really to go with simple designs. In that case you find solutions that are all of well-vetted, fairly dependency free, fast and memory-frugal.
I think CGI::Application, CGI.pm, and HTML::Template would all generally fit here.
Just because a solution is simple doesn't mean it has to be a compromise or not complete. There was a day when these kind of solutions were referred to as "elegant".
Re: (Score:2)
I think you're missing my point. There's no one solution that meets everyone's needs.
Simple is good, but simple is relative to the person and problem. CGI::Application seems a bit too simple for my needs. OTOH, I think Jifty is too much. That doesn't mean either of those solutions is wrong for someone else. I'm sure for some people CGI::Application is just enough glue, and for others Jifty makes their life much easier.
For me, CGI::Application, CGI.pm, and HTML::Template don't work so great. They work for yo
Re: (Score:1)
I meant to convey that I do very much agree with this point.
I just wanted to extended it to clarify that sometimes there are actually sweet spots between choosing features which seem at odds which each other.
Partly we are acknowledging that people have different underlying philosophies about what a good balance of features is, so what I consider a sweet spot may not seem like one to you.
This is an important discussion to
Re:well said (Score:1)
I'd like to see the Perl community adopt an attitude of "Make the default not suck for everyone".
Reply to This
Parent