3 ms·
I don't see it as so much of a performance issue as a usability issue. Tornado uses eval for parsing templates. The nice effect of this is that you write Pytho
by m0th87 16y ago
I don't see it as so much of a performance issue as a usability issue.
Tornado uses eval for parsing templates. The nice effect of this is that you write Python snippets in your templates rather than learning an entirely new DSL for it (like in Django). It's pretty nice as long you're disciplined enough to not put business logic in the templates.
- IgorPartola 16y agoEek. Sorry, I disagree. IMHO, templating engines should not allow you to do much more than simple substitution, loops and escaping. I think Django strikes a very nice balance and learning to use it takes minutes. This is like saying that you should be allowed to use ASM in your Python code, as long as you promise never to actually do it.
- m0th87 16y agoSay what you will, but I find my Tornado templates much less verbose than in Django, even when respecting the rules of "proper" templating. Also, I just realized you're my former coworker. Hi Igor, it's Yusuf :)
- IgorPartola 16y agoSmall world!