anchor.diff:  explicit calls to callable from templates, has better performance and has a plugin
   system, etc ...
   
  -Django comes with jinja backend, why I should use *django-jinja*?
  +Django comes with jinja backend, why should I use *django-jinja*?
   
   The Django builtin backend has very limited set of features if we compare it with
   the django template engine and in my opion is not very usable because it does not
  
positive.code: [NOTE]
  ====
  If you are using the default value for app templates directory for
  django-jinja backend, take cara about the order template engines, because the
  django-jinja backend by default uses the same directory for the templates that
  the django template engine. If you put the django engine first every jinja
  template will be found by the django engine.
  
negative.code: {{ url('ns:name', pk=obj.pk) }}
  ----
  
  This approach is very flexible, because we do not need additional options to set a result
  if executing url in one variable. With jinja2 you can use the set template tag for it:
  
  [source, html+jinja]
  