Earlier quoted context omitted.
> When you use a templating engine, you can change the backend entirely without messing with the template. You can also compile/optimize the display of data in the template more easily. To be fair, all that you can do with a templating engine you can do "natively" as well. You can for example have code-less templates in PHP if you are disciplined enough to keep it that way. The only thing template engines do is enfor…
Sorry, should have clarified "code-less". I definitely don't like logic in templates (although React is making me re-think that as a strict policy). But I actually meant code as in any code. A line in PHP might be this: ">Some link So that "echo" is the code. And the same thing in Jinja is this: Some link In Jinja, it's only HTML + the names of variables (which I guess you could call "data"). I can now take that line…
">Some link
Which is effectively pretty close to a templating pseudo-syntax.