What is it with #templating languages and math? Does a string-injecting system _really_ need full-blown mathematical operator set? I’m looking at multiple templating langs, and they all seem to be far from an optimal state where the emergent behavior appears:

- #Liquid: No math, relies on #JavaScript and benevolence of #Shopify / #Microsoft

- Liquor (by @whitequark✧✦Catherine✦✧): Includes math and lots of operators in general, too powerful to be interesting

- #Handlebars: require #JS

- #Mustache: No arguments to partials, thus no abstraction and data passing

- Server Side Includes: Have everything I need, but are #Apache -specific in many ways

Uuuuuuugh. I would’ve gone with either of these for my website and day-to-day programming, but I don’t want to commit to either an explicitly Turing-complete system or non-portable JS-heavy one.

I guess I’m still staying with #ed (1) until the state of templating improves. Or until I write a #Lisp version for any of these, likely SSI.