# Improve sub-lange support for template literals

**URL:** <https://es.discourse.group/t/improve-sub-lange-support-for-template-literals/1529>\
**Category:** 💡 Ideas\
**Created:** [November 21, 2022, 3:19pm UTC](https://es.discourse.group/t/improve-sub-lange-support-for-template-literals/1529 "2022-11-21T15:19:05Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![WebReflection](https://yyz2.discourse-cdn.com/free1/user_avatar/es.discourse.group/webreflection/32/248_2.png) [@WebReflection](https://es.discourse.group/u/WebReflection)\
**Post date:** [November 21, 2022, 9:38pm UTC](https://es.discourse.group/t/improve-sub-lange-support-for-template-literals/1529/8 "2022-11-21T21:38:38Z")

</div>

I've answered relevant questions to this conversation in here:

> [@Proposal: ESX as core JS feature](https://es.discourse.group/t/proposal-esx-as-core-js-feature/1511/29):
>
> for clarification sake, I'll answer these first: Why can't template tags support this? because there's not standard syntax around string chunks in a template literal. ESX (and JSX) is syntax. So spreading that way in library-x tag will produce the unexpected in library-y tag. In ESX there won't be any issue. It's true that syntax errors won't be thrown until you're actually running that piece of code, but that but is a show-stopper for developers if you're tagging with a built-in tag,…

I also believe tools are not the answer for the simple reason there's no standard around how HTML or SVG or even SQL can be written in template literal tags ... anyone can bring in its own sugar, like `@click` in lit-html did, while _ESX_ is about standardizing a syntax everyone can understand.

The root issue about not being ble to just add your tool to the equation is this: there is no standard in how people can write strings, and the fact they can put anything in a string is actually the strength of template literals tag based solutions, but it falls shortly in terms of advantages compared to the de-facto JSX standard. ESX wants to bring both world into syntax anyone can consume and understand, same way template literals tags do already, but every library in its own special way. Fragmentation is bad for standards adoptions, we all now that, which is why I don't understand this conversation, as it's focused on highlight and tools, while the issue is the inability to have a standard way to define, and understand, tree structures in ECMAScript, and literally nothing else.

---

_[View the full topic](https://es.discourse.group/t/improve-sub-lange-support-for-template-literals/1529)._