This comment from the Django documentation was pointed out to me tonight and it winds me up a bit:
Oh, and one more thing: Making humans edit XML is sadistic!
There's a few things in this comment that annoy me.
Most websites are written as HTML. Almost every site these days is XHTML. And XHTML is "A Reformulation of HTML 4 in XML 1.0". At this point yes I'm aware, XHTML isn't quite XML as this article points out, but it's as near as damn it. Everyone writes XHMTL these days. In fact look at the heading HTML of the Django admin interface:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en-us" xml:lang="en-us" >
So how can you write an interface in XHTML and claim that forcing people to write in XML is sadistic? The difference is so small to be neglible..
In fact in Plone e-mails are formed using Page Templates, here's a snippet:
From: "<span tal:replace="portal/email_from_name" />" <span tal:replace="structure lt"/><span tal:replace="portal/email_from_address" /> <span tal:replace="structure gt"/>
mail_password_template line breaks added for readability
I would accept that is a little complicated and personally I've always found using python string formatting (the % operator) more than sufficient. So we don't need Django templating for that either. But let's face it, in most sites I have done, 95% of the templating demands are for HTML. I bet yours are too. So focus on what you need to do the most and build good tools that allow you to do it fast and simply with great flexibility.
Throwing out a great tool for an edge case, which it allegedly can't meet, is not a good answer. There's better reasons for not using Page Templates and I bet in any feature comparison, Page Templates would beat Django templates. Just say "I don't like Page Templates, it's ok".