Me: So we've used Bootstrap for front-end and Django for ...
Teacher: Bootstrap is not a front-end framework.
Me: Uh..Okay. It's a CSS framework ? My bad.
Teacher: No, Python is for front-end.
Me: You mean templating ? Yeah! We've used Jinja templates.
Teacher: No. Use Python for front-end.

wanted to parse jinja templates for parameters to be collected at runtime.
Python - 4 lines and done
Java with jinjava library - did not get anything done, lost some hair going throught their highly undocumented code.

jinja templates make me look towards html in a whole new light. are we 'inserting' data to an already rendered page? am i really mixing server code with ui ? It doesn't feel so. there are if else and loops being executed for html code, like wtf?

I don't know but everything feels so good. like i was literally hating every piece of website i was writing in php. everytime i wrote <div>....</div> followed by <?php ... ?> followed by another html tag /php tag in a fuckin php file, i wanted to kill someone from w3c.
WHY THE FUCK ARE WE ALLOWING THE MIXUP ?WHY IS PHP FILE HOLDING HTM TAGS? WHY?WHY?WHY?

But this... this is beauty. their is separation of concerns. jinja has some big powers, we can loop, repeat, make clauses, inherit other html classes, load html content into blocks, set variables,
but main concepts like file handling, response/request handling,calculations,etc are all being done in separate python files. I know that these jinja templates also might be running python in background, but atleast a developer cannot fuck up that code.
we can be sure that if correct jinja codes are written in html, then it would load correctly. And wherever devs doesn't fuck up, the output is better to understand and more maintainable/scaleable