Home > Articles > Using PHP as Your Template Engine > Page 6/6

PTE - Page 6

Conclusion:

I am not willing to do the following things for a template language/specification:

  • Write documentation when I can simply point people at www.php.net/echo (or whatever part of the language they need help with)

  • Put the effort into supporting every feature someone might need in a custom template engine through custom programming to create new constructs in a template language only to tie it back into the PHP language anyway - why not just use PHP as the template engine and utilize the power it offers.

  • Increase the load times of my web pages due to parsing (a lot of times regex is involved) and rendering via code when PHP is natively compiled into binary form, and is loaded and running in memory all the time (when loaded as a module)

For my money, I would rather avoid the complexities of templating engines and go with a widely supported, widely known and understood, powerful template engine called PHP.

Jump to page: _1_ | _2_ | _3_ | _4_ | _5_ | _6_

Thank you for reading! Feedback may be left by using the contact form
Interesting and/or informative comments will be posted on the article comment page.


For web site hosting I recommend - www.bluehost.com