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: 
  As we said previously, django-jinja backend for django 1.8, uses the same
  directory for templates as the django template engine. But in some circumstances
  you may want to change it for use other directory. You can overwrite the default
   value with `app_dirname` option:
  
  [source, python]
  
negative.code: 
  === Context processors support
  
  It is a helper to use django's context processors with jinja2 backend
  for django 1.8.
  
  .Example setup a bunch of context processors:
  