PhpRiot
News Archive
PhpRiot Newsletter
Your Email Address:

More information

PHP as a templating language

Note: This article was originally published at Planet PHP on 15 May 2012.
Planet PHP

There's been quite a bit of talk, recently, in PHP-land about templates and the ramifications of enforcing aopurea PHP scripts by preventing scripts from entering html mode. I'm not quite sure how I feel about this RFC, but it got me thinking about the whole idea of using PHP for templating in modern web apps.

For many years, I was a supporter of using PHP as a templating language to render html. However, I really don't buy into the idea of adding an additional abstraction layer on top of PHP, such as Smarty (and many others). In the past year or so, I've come to the realization that even PHP itself is no longer ideally suited to function as the templating engine of current web applicationsa-aat least not as the primary templating engine for such apps.

The reason for this evolution is simple: modern web apps are no longer fully server-driven.

PHP, as you know, is a server technology. Rendering html on the server side was fine for many years, but times have changed. Apps are becoming more and more API-driven, and JSON is quickly becoming the de facto standard for API envelopes.

We can no longer assume that our data will be rendered in a browser, nor that it will be rendered exclusively in html. With Gimme Bar, we render html server-side (to reduce page load latency), in JavaScript (when adding or changing elements on an already-rendered page), in our API (upcoming in a future enhancement), in our iPhone app, and certainly in other places that I'm forgetting.

Asset rendering in Gimme Bar can be complicateda-aespecially for embed assets. We definitely don't want to maintain the render logic in more than one place (at least not for the main app). We regularly need to render elements in both html and JavaScript.

This is precisely why we don't directly use PHP to render page elements anymore. We use Mustache (and Mustache-compatible Handlebars). This choice allows us to easily maintain one (partial) template for elements, and we can render those elements on the platform of our liking (which has been diversifying more and more lately, but is still primarily PHP and JavaScript).

Rendering elements to html on the server side, even if transferred through a more dynamic method such as via XHR, really limits what can be done on the display side (where aodisplay sidea can mean many things these daysa-anot just browsers).

We try hard to keep the layers our web applications separated through patterns such as Model/View/Controller, but for as long as we've been doing so, we've often put the view bits in the wrong place. This was appropriate for many years, but now it is time to leave the rendering duties up to the layer of your application that is actually performing the view. This is often your browser.

For me, this has become the right way to do things: avoid rendering html exclusively on the server side, and use a techonology that can push data rendering to your user's client.