undefined | Better HN

0 pointssimonw11mo ago0 comments

Yeah, the template language was strongly influenced by NOT wanting to allow arbitrary logic like PHP does. I was already a fan of Smarty - https://www.smarty.net/ - which did a great job of separating out presentation logic in PHP.

I've been using Jinja for my own projects for a few years because I wanted more expressive Python code in my templates! I think we didn't quite get the balance right for that in Django.

0 comments

3 comments · 1 top-level

robertlagrant11mo ago· 2 in thread

I think a great combo would've been Django's features, packaging and most importantly documentation, but with SQLAlchemy and Jinja2 technologies underneath.

jefurii11mo ago

The nice thing about Django is that there's nothing stopping you from doing that. You'll have to give up the Django Admin if you use SQLAlchemy for models but you can still do it. I have several projects that use Elasticsearch as a backend and one that's based on JSON documents in Git repositories. You can totally do it!

frankwiles11mo ago

That would have been hard since both of those projects came out after Django, but just an FYI Jinja2 templates are supported and nothing stops you from using SQLAlchemy. Granted you lose a lot of the tight intergration that makes Django great to use.

1 more reply

j / k navigate · click thread line to collapse