> That StackOverflow question seems unrelated because it's asking about untagged template literals. The first answer reinvents tagged templates and the second

> That StackOverflow question seems unrelated because it's asking about untagged template literals. The first answer reinvents tagged templates and the second suggests them. I thought it was a good example to show the complexity of hacking in this approach. I'll add more context in the future. I'm agreed that the average developer would hate working with an an AST -- JSX covers 99.9% use-case and React codebases are full of functional programming escape hatches -- but it is the foundation. An HAST is an interoperable, extendable representation we can move between any framework or tooling. I'm likely projecting too much on the proposal. Templating is the top priority but it's the ancillary bits you mention that excite me most. > Markup-based templates look like the output I made the mistake of drinking functional programming laced koolaid, so in my mind they really do translate well, but I respect that you have a broader perspective. Thanks for taking the time to reply. I'm a smidge honored that you'd even review my feedback!