I disagree that the way is "worse". I like that in templates, string handling is _enforced_ to be different. For example, when you manipulate strings in templa

I disagree that the way is "worse". I like that in templates, string handling is _enforced_ to be different. For example, when you manipulate strings in template, you can be reasonably sure all output is escaped, unless you specify otherwise in a very few precise cases with explicit syntax. A good template language allows you to create/limit available tools/helpers for your particular project. That is especially important in larger projects and larger teams, where everyone is not immediately expected to know intended good practice to follow. Creating DSL in template _is_ a way of documenting intended good practice. A good template language does not pretend not to be turing-complete: instead, it provides comprehensive error handling and error messages, so that users know exactly where some error or type occurred. One more reason to use the language is because it is a language. If someone used something like Django, the Twig will be quite familiar and easy to pick up. Template engine can optimize-away, pre-compile things, just like languages do. With separate template language you don't need to recompile whole build if you change a template (presuming hosting language is compiling to binary and template engine is interpreted). Full disclosure: I am currently rewriting Twig in another language, and believe it's completely worth the effort.