http://www.perlmonks.org?node_id=769955


in reply to Re: web-dev and perl (mason, catalyst, embperl)
in thread web-dev and perl (mason, catalyst, embperl)

It's purely a personal style thing, but I tend to pull out CGI::Application even for my simple/one-off stuff. Why? Well, my one-off stuff almost always evolves into (2 .. $n)-off. Eventually my planning patterns just evolved into a make-way-for-change approach.

Mostly I'm still haunted by the memory of a script that I'd planned as one-off but kept using for years. I still see that ugly code staring at me in the middle of the night.

You might not have the myriad assortment of issues that I do, though.

  • Comment on Re^2: web-dev and perl (mason, catalyst, embperl)

Replies are listed 'Best First'.
Re^3: web-dev and perl (mason, catalyst, embperl)
by Your Mother (Bishop) on Jun 09, 2009 at 16:39 UTC

    You are wise. I usually "inline" my Template/Alloy template in the __DATA__ (with blocks representing different wrappers/fragments) of a one-off so it ends up being both fast to write and easy to break out if I have to later. I like CGI::Application and I think it's one of the right ways to do it; for me personally it falls between too little (doesn't cover what Catalyst does) and too much (I can write dispatch table and such for a straightforward CGI in a few minutes).