←back to thread

Django: what’s new in 6.0

(adamj.eu)
379 points rbanffy | 2 comments | 09 Dec 25 20:33 UTC | HN request time: 0.41s | source
Show context
giancarlostoro ◴[09 Dec 25 21:10 UTC] No.46210692[source]▶
Template partials look good, which is one of the key reasons frameworks like React are as good and popular as they are, because you can reuse small segments of code.
replies(8): >>46211187 #>>46211247 #>>46211354 #>>46211402 #>>46211982 #>>46212701 #>>46212849 #>>46213424 #
pier25 ◴[10 Dec 25 02:44 UTC] No.46213424[source]▶
Amazing that Django didn't have this until 2025
replies(2): >>46215377 #>>46216931 #
Hamuko ◴[10 Dec 25 08:21 UTC] No.46215377[source]▶
Wouldn’t Jinja2 macros count?
replies(1): >>46218507 #
1. sgt ◴[10 Dec 25 15:08 UTC] No.46218507[source]▶
I stayed away from Jinja2 ... was under the impression it has lower performance. But I could have been wrong all these years.
replies(1): >>46223832 #
2. Hamuko ◴[10 Dec 25 21:04 UTC] No.46223832[source]▶
>For nearly all cases, Django’s built-in template language is perfectly adequate. However, if the bottlenecks in your Django project seem to lie in the template system and you have exhausted other opportunities to remedy this, a third-party alternative may be the answer.

>Jinja2 can offer performance improvements, particularly when it comes to speed.

https://docs.djangoproject.com/en/6.0/topics/performance/#al...