I recently built some templating language (rather an intermediary language for documents) for solving an accumulated frustration over the years. Already added into four or five of my projects (for templating html, emails, dashboards, chatbots messages, and some configs).
replyThe design point "deterministic, hostable, with enough to make hooks from the templates" is what makes it special: https://lucasdicioccio.github.io/tramaj/ .
I always thought that the type-safe XML/HTML in Ur/Web was elegant.
replyFor examples, see http://www.impredicative.com/ur/demo/
There was a brief period where everyone and their dog implemented mustache[0] as a template system, but it died quickly because cross-language templating is not that useful in the end, you seldom need to switch host language but keep the templates.
replyI think the craze was about "purity" of mustache as presentation-only template engine. Apparently you need some level of logic to be useful.
replyType safe DSLs in Kotlin
replyCopied from Groovy Builders, here's an example from 2009: https://blog.mrhaki.com/2009/10/groovy-goodness-creating-xml...
replyI think nim also has this.
replyAs for Django... well.. Django only has text formatting, you can write any garbage and broken html and lots of invalid templates with silent failures there unfortunately.
We created https://htpy.dev to solve this for our Django app. Has been using it in production for multiple years. Works great with Django (or any Python web framework).
replyOh that looks cool :)
replyThis had me checking if anyone has implemented first-class support for Python JSX components in Django yet, and it could be... sort of... maybe viable with PyJSX? [1]
replyIt looks like you'd have to implement something equivalent to provider/context functionality yourself if you want it, as well as a simple render()-like helper to render a component tree. I've not tried their VS Code plugin, but it's a good sign that they have one.
This is sort of halfway between tsx and Elixir's EEx
reply