Where did you get that information from? Whether the content is "slightly" dynamic or "heavily" dynamic shouldn't matter. Time is spent to load the template and process it, more processing means more CPU time, but this by no means constitutes "not an appropriate solution."
And the conclusion that is hinted at ... that HERE DOCS are better for "heavily" dynamic content than templating solutions seems very absurd to me - especially when you realize that templating solutions allow you to abstract away components that can be included and cached ... have fun trying to accomplish that with HERE DOCS.
I really get the impression that most advocates of HERE DOCS have not fully grasped just how much there is to be gained by switching to a templating system. They are both great tools, but the latter is a much better fit for delivering Web Applications.
UPDATE: (a reply)
HD with interpolation is indeed already a simple templating
system, but it's one that will allow you to paint yourself
into a corner. Do yourself a big favor and start using
Template modules more than you already might be,
then you might realize that HERE DOCS are only good for
quick and dirty solutions. (I really believe that you have
only a cursory experience with Templating modules - i did a
search on your past nodes and none of them mention a single
word about Templating except the ones in this thread.)
Besides, aren't you just needlessly reinventing the wheel?
;)
Oh, and believe me ... i do this for a living.
jeffa
L-LL-L--L-LL-L--L-LL-L-- -R--R-RR-R--R-RR-R--R-RR B--B--B--B--B--B--B--B-- H---H---H---H---H---H--- (the triplet paradiddle with high-hat)
In reply to Re: The scope of templates
by jeffa
in thread I need a title - sucka! :-)
by PetaMem
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |