Re: Template engines
| From: | Robert Cummings | Date: | Tue, 09 Nov 2010 05:23:43 +0000 |
| Subject: | Re: Template engines | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-309394@lists.php.net to get a copy of this message | ||
On 10-11-09 12:20 AM, Paul M Foster wrote:
On Mon, Nov 08, 2010 at 02:41:12PM -0700, Hansen, Mike wrote:Aaaah, the great argument that uses a single brush to paint all template engines into one corner because if you've used one, you've used them all... Seriously? Cheers, Rob. -- E-Mail Disclaimer: Information contained in this message and any attached documents is considered confidential and legally protected. This message is intended solely for the addressee(s). Disclosure, copying, and distribution are prohibited unless authorized.I really like the idea of using a templating engine. Which one do you use? Why? For those that don't use templating engines, why don't you use them?Here's why I don't use a templating engine. First, You're taking an embedded language and writing a templating engine in it. Seriously? Second, you're painting a single page, maybe 10-15K worth of information, and you're dragging 100K of code around just to paint a single page. Seriously? Third, you're creating a page on the fly, thrashing the server's CPU in order to generate a page which could be built statically, or at least with minimally embedded PHP. Seriously? Fourth, you could achieve the same end result with carefully crafted PHP embedded in your static HTML file, with actually very little more work. I know, everyone's heard this before. But just because you *can* do something doesn't mean you *should*.