jinja

I don't really know what the latter would mean, since nix is a programming language and jinja is a (string-based) template system.

Heavily inspired by jinja2 And Jinja is an extended reimplementation of Django's template language.

Or build a separate language like Haskell's Hamlet [1], or Python's Jinja [2].

I switched to Flask mostly because I always ended up ripping Django apart: - Jinja instead of Django templates.

I suppose you could use jinja and bash -- but why pull in two full interpreters as a dependency?

If I'm at the point where I'm doing templating with key:values, I'll be using jinja.

Or do you actually want to use jinja with nix somehow?

Just an FYI, the newest version of Django (1.8) now supports Jinja or Django templates by default and you can plugin other templating engines if you want.

Do you wish nix's syntax were more like jinja?

However, I am not a huge fan of the syntax[1], and rather use a template engine I am quite familiar with (like jinja).

If I'm being honest, just the thought of writing dozens of sed and awk commands to mimic the templating offered by Jinja gives me hives.

I've never used or seen jinja before but it definitely has a few features that I'm thinking of adding like block so thanks for the link.

The biggest issue probably was for the library developers (Django, Flask, Jinja, pymongo etc) to create a new Py3 package.

Just as you can swap out Django's default homegrown templating system with Jinja, you can swap out Meteor's default homegrown reactive frontend with React.

I used to think PHP was good for templating, but then I learned about code-less templating engines like Jinja, and I'll never go back.