fplanque: dev blog

"in b2evo, you can't always trust the template/skin"
I so much agree...

PHP is a templating engine, ofcourse, but other (PHP based) templating engines are abstraction layers between template itself and program code. Template creator will need to know only small subset of commands, and will be able to create affordable templates to use with some product. It allows to separate program development, and design/templates creation, and to increase modularity and scalability of product ;)

Also, templating engine is needed when you must solve some specific problems in a shortest possible time.

What's the problem with the template creator only using a "small subset of commands" of PHP? Are template creators genetically unable to type <?php and they have to type something else like %% instead?

For the rest, I won't even argue. I didn't say that templates are useless, I said that you don't need yet another language for them. (Actually I *did* say that templates are oftentimes a bad idea, but that's another story...)

"Templates are oftentimes a bad idea" - right words :) But sometimes they're good idea IMHO.
I don't think, that all template are genetically deviated species. But difference between php and template engines isn't in opening and closing tags, am I right? They are implementing different conceptions of coding.
As a programmer, I think, that you are right, and use of PHP is more efficient, than use of any php-based TE. But, sometimes, template engine is more convenient way - for me, and for maintainer of my product (website). IMHO.

Correction: "I don't think, that all template creators are genetically deviated species".

I don't think you are right, precisely! The only real difference between PHP and template engines *is* syntax! (opening/closing tags and a few other details).

Once again, the only benefit of a templating *engine* (not talking about templates altogether here) is to filter out harmful PHP features if you don't trust the template author, which should not be the case if *you* are the author.

Benefits: abstraction from main code modules; intensive code reuse; easy integration; customizable syntax; built in smart caching possibilities (some TE's); TE can be implemented as PHP module (efficient?); design can be changed without changing main program code - I really don't trust _template_ author... sometimes...

yeah yeah yeah ... a zillion arguments for properly structuring your PHP and still only one for template engines: when you don't trust the template...

(PS: I have nothing against using a cacheing mechanism -- But that's yer another off-topic suggestion -- I just don't think you need to wrap your cacheing into a templating engine.)

Khm... Yeah. You're right. Ok 8)