eelixduppy - 3:07 am on Nov 18, 2011 (gmt 0)
it's got me thinking of something along the lines of...
This is looking awfully a lot like what Smarty looks like with a lot less flexibility.
They increase overhead in general
I find it hard to believe any web apps are mission critical services requiring perfect optimization with virtually no overhead. If that were the case, you wouldn't be using an interpreted language in the first place. Trust me, Smarty's overhead is minimal and will go unnoticed; it even has a caching mechanism built in if you choose to use it.
With templates the code maybe more manageable but it splits over multiple files and takes longer to debug or change something.
This to me seems to contradict itself. If code it more manageable, how does it become harder to manage? ;)
I know most people here work on their own websites alone but using a well known templating framework such as Smarty allows someone who is unfamiliar with your website to come in and just start making changes. Plus, you don't need to spend valuable resources on maintaining a proprietary framework.
But if you are really inclined and want total control over how your template framework operates, Smarty (as well as others) are completely open source projects. Have at it -- at least you'd be starting with a pretty solid base to work from.