There are a few problems with Christian's assumptions: * Not everyone uses a JS Framework. Personally, we use a lot of static pages, and when we do want to do some fancy stuff, we use pjax<https://github.com/defunkt/jquery-pjax>to replace content on the page, but in the backend this is still done by rendering a full template through a Django view. * The templating language is also used for small stuff, and the switch to Jinja would enable using the templating language for even more stuff. The biggest issue that comes to mind are template-based widgets<https://code.djangoproject.com/ticket/15667> .
Personally, I'm in favor of switching to Jinja. The speed bonus and the ability to call functions with arguments are great features for me. One downside I can think of is that Jinja does not escape variables by default, which might become a XSS security issue. On Wednesday, February 12, 2014 9:10:29 AM UTC+1, Christian Schmitt wrote: > > I'm not a django-developer, but I'm creating a lot of applications with > Django and I would never want to switch to Jinja2. > > Why? > > The first thing is that Django Templates are simple to understand, they > are not formed as a new DSL or a Programmable way of a Template language. > Their Syntax is clear and simple and it's really easy to extend the tags > for new programmers aswell. > > I only had a quick overview of Jinja2 but the Syntax aswell as other > things just looking more like a programming language for templates than a > simple templating engine. > > Also the Template Language or the Django interface is most of the time not > the bottleneck of any application (there are some exceptions where the > template engine or some django views will be a bottleneck but most of the > time there is a easy way to solve it like using c) > Nearly 90% of the time you will have trouble with the database. > > Changing the Template Language will maybe looking good on benchmark > papers, but i don't think that it will help scaling websites to need less > servers. (Django also has a really good and easy way to scale up really > good, thanks to the DatabaseRouters, Cache Engine, Session Engine, etc. you > could Scale out/up really, really well) > > The next thing is that the internet is changing and template languages > that are on the server side getting less focus. > Mostly applications are more and more and API which will getting consumed > by a Framework like AngularJS or KnockoutJS. > So there is no need for a faster template language, since the Django > Template Language is fast enough for the Django Admin or other applications > where a Template Engine is still needed. > > I hope that the most people understood my points and that my english isn't > too bad. > > For me switching to jinja2 wouldn't make any sense. > Also we changed a lot of app loading stuff, so my applications needing to > be migrated. While I think that I have a lot of stuff that needs to be > refactored when I switch to Django 1.7 I don't want to have a lot of > backwards incompatible stuff in Django 1.8 or Django 1.9, too. > > > > > > 2014-02-11 14:07 GMT+01:00 Aymeric Augustin > <[email protected]<javascript:> > >: > >> 2014-02-11 13:42 GMT+01:00 Christopher Medrela >> <[email protected]<javascript:> >> >: >> >> >> >>> What did Armin said about Python 3 exactly? >>> >> >> He wrote an extensive argumentation about "why Python 2 [is] the better >> language for dealing with text and bytes" [1] as well as a number of >> tweets >> and a few other blog posts along the same lines. >> >> While his arguments are technically correct, I disagree with his >> conclusions >> because he's speaking with the point of view of an expert maintaining >> libraries at the boundary between unicode and bytes (like werkzeug). >> However, >> most Python users aren't experts and aren't maintaining such libraries. >> In my >> experience working with Python programmers ranging from intern to >> veteran, the >> unicode model of Python 3 is a strict improvement over Python 2 in terms >> of >> pitfalls hit in day-to-day programming. YMMV. >> >> [1] http://lucumr.pocoo.org/2014/1/5/unicode-in-2-and-3/ >> >> -- >> Aymeric. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to >> [email protected]<javascript:> >> . >> Visit this group at http://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/CANE-7mU31zMRkVrJAZY_tde-xdiU63p2s38pB2vVPpeDpPBkxQ%40mail.gmail.com >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/87a7fec1-b806-42f1-9ed1-3d167a9bfd2f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
