The caching is a big plus too. Thanks for reminding me!

PHP really has no connection pooling at the DB level. So unless this changes, the caching is a MUST. Otherwise the DB queries are going to kill any site of moderate traffic.

Good call Mith.

PS-You are right Smarty does get abused too. But it can not get pushed as far as PHP in the code. Look at JAVA, JSP and JSF. These are moving in the oposite direction, more toward a templating engine and less to straight java to do display.

Can it be done in all PHP... sure. But I think that removing the template system is a big step backwards!

Quote:
What I was talking about was "abuse" in the way of

<{php}>
Normal PHP Code here
<{/php}>

that can be pushed just as far as PHP in the code - as it IS PHP in the code.

Wow!

Quote:

As I did not know Smarty did this.... I was not aware of the danger.

That CAN be abused to the full extend then... But I still think that the general templating nature of smarty keeps it cleaner.

If you have to include
<{php}>
Normal PHP Code here
<{/php}>

Then you are doing something very wrong. (Wrong: against the design pattern)

As usual, Mith teaches me something. Thanks!