Reflections on template engines

This week many times thought about the further modernization of the samopisny template system. The irresistible craving for beauty does not leave him alone. In addition, the unexpected experience with XSLT as a template engine gave additional food for thought.
By the way, two topics appeared at once ( techniques for working with a template maker , Native template maker ), which describe methods of working with native php templates, so to speak, with the trump template.
For some reason, all comparisons are reduced to Smarty or similar. Own development in the calculation for some reason, little is taken. In this regard, like the comments :

I think that the fear of using their own development in a team is primarily due to poor communication. Improve your communication environment and it will be better! What are 10,000 lines of your documentation worth if a newbie has a specific problem? and what if this problem was not previously discussed? wait for a new release, rummaging through the codes of the finished product (which often looks like a black box)?
In general, I am FOR the use of ready-made solutions, but sometimes this is not justified.
In particular, the fear to teach other people how to use your solution is not justified; if the solution works, and the code is normal, then most documentation will not be needed.

The problem of the habrauser with the slow work of ob_start () was very amusing. But then it dawned on me why with native templates, buffering is needed - all data is inserted into them through echo =). It turned out that using sharp patterns like diarrhea and native templates, the entire gain in speed is enhanced by buffering.