Talk:Case against templates

http://www.raditha.com/php/ has a bad link: "The case against templates" links to http://raditha/wiki/Case_against_templates but should be http://www.raditha.com/wiki/Case_against_templates .

I disagree

I developed the CMS for my website. I started coding this CMS without any template engines but after a while I totally messed up the PHP in an attemp to redesign.

Now i'm using patTemplate, Its now easier to write codes, easier to redesign and i must say that its way faster than before.

This isnt 1995 any more so stop worrying about server load. My site is running on a dual Xeon with 2 GB RAM. If your server cant take that simple load, get a better one.

I have 12 loops in a page of my site. It also uses Output Buffer. There are 1156 lines of codes but it still doesnt take more than 0.01 sec to execute.

-Azad

I Also disagree

Suppose a web designer joins your team; with no need/desire to know or see SQL. They're artists, not programmers, and thus there is no sense in making them look at the logic behind the code just to change the user interface. With a good templating system, designers can easily maintain their layer of an application and programmers can maintain theirs in their own comfortable world. The benefits usually justify the overhead.

-beeplogic