in reply to Best way to start a perl project

I agree with Discipulus that #3 is the only sane choice for applications that are either large or likely to grow. I donít really recommend Template::Toolkit. This is not because I donít like it, I do, itís really wonderful, but itís so deep that it crosses the boundary of template engine and moves into mini-language. Itís also very slow compared to some of the alternatives, including Template::Alloy which can use Template::Toolkit syntax; so itís the way to go if you want that. Text::Xslate feels shallow by comparison but itís closer to the ideal of a view (only does presentation and the most basic logic/code and it is variable context ignorant which is kind of unPerly) and itís terribly fast. As far as that goes, speed in the template layer is not always a prime concern. Depends on the application. Both TT and TX cache templates for performance improvement too.

Update: typo fix, grazie mille, Discipulus.

Replies are listed 'Best First'.
Re^2: Best way to start a perl project
by Discipulus (Abbot) on Jun 01, 2017 at 11:15 UTC
    thanks Your Mother for many useful hints,

    if i recall it was possible to cache templates generated by Template Toolkit speeding it up a lot, or I'm wrong?

    oops.. it seems i've not read the whole post. sorry ;=)


    There are no rules, there are no thumbs..
    Reinvent the wheel, then learn The Wheel; may be one day you reinvent one of THE WHEELS.