Re: The hidden charm of Template::Toolkit (and templates generally)

[naikonta]

It is safer, since the template developer has no access to naked Perl. It also seems of no concern because the template developer is me or my office mate.

IMHO, it's not because the template developers have access to "naked Perl". Rather, it's to protect them from having to code in complex programming language. The term "separating content (data) from display (view)" is really for roles in development instead of persons. I'm mostly a team on my own (except when I'm in a Real Team) so I need to think as programmer when coding Perl, think as designer when preparing the template, for instance.

I know it's hard to switch repeatedly among Perl, SQL, CSS, JavaScript, and HTML (not to mention various types of config file), all alone at once. Sometimes I don't know which one drives another :-) But once you (if you happen to be a single fighter (yes, for now)) get the rythm, you'll have some fun. As a bonus, when you have a company or two, the only thing they need is to read the rules or specs or whatever it is to join the team as whatever role they'll play.

To the question and examples at the end of your node, it's very clear. In your "pure" Perl implementation, "you" are thinking twice over two things in one session. In the templating solution "you" are thinking once for each thing in one or two sessions.