Re:Dropping Django
by paulgb on Wednesday August 19, 2009 @05:58PM
(#773887)
The article gave some examples that I've run into myself: using email addresses instead of usernames for authentication, and adding additional fields to the User class. I also dislike the template language. Why invent your own language and control structures when everyone using it knows python? Mako (http://www.makotemplates.org/) does a good job of not reinventing the wheel.
[ Parent
| on HN ]
Re:Dropping Django
by mtrichardson on Wednesday August 19, 2009 @06:21PM
(#773928)
One of the main assumptions behind the Django templating language is that you don't need to know Python.
http://docs.djangoproject.com/en/dev/misc/design-philosophie...
"The Django template system recognizes that templates are most often written by designers, not programmers, and therefore should not assume Python knowledge."
In my experience this has often been the case.
I figured that had to do with it, but it doesn't really explain why they don't just use an equivalently powerful subset of python. Better yet, allow full python like Mako does, and let the designers decide what subset of that to use in templates.
Re:Dropping Django
by racketman4 on Wednesday August 19, 2009 @08:07PM
(#774142)
The template language isn't for you.