5 ms·

indeed the vintage templating was a logical bottleneck

• f311a 11mo ago
  How is it different from include? Just less files from my perspective
  • chistev 11mo ago
    I asked the same question
  • simonw 11mo ago
    The "inline partials" feature is neat, means you can use and define a partial at the same time. The way you can render just a named partial from both the render() shortcut and the include tag is nice too: https://docs.djangoproject.com/en/6.0/ref/templates/language/#template-partials https://docs.djangoproject.com/en/6.0/ref/templates/language...
    • f311a 11mo ago
      Yeah, but I was doing the same thing 10 years ago with include mixed with extends and blocks. I can just include a file inside a template or render it directly.
  • agumonkey 11mo ago
    you're kinda right, {% partial ... %} vs {% include ... %} is not a big difference, but my mind was vaguely thinking that "includes" have often been seen as large templates, whereas partial have been after the component era with the idea of making small blocks. (my 2 cents)