> yes we do now know what good syntax for templating is, it's basically jsx (and I'm saying this as someone who's really not a fan of React). It took the whole web by storm, it's been adapted for all kinds of frameworks, and it's undeniable that all js templating systems converged towards common attributes: templates-as-expressions, composition via nesting and control flow with just javascript (instead of specific template syntax).

This is not true. For instance:

Vue uses markup-based templates like this:

    <ul>
        <li v-for="item in items">
            {{ item.message }}
        </li>
    </ul>

Svelte uses text-based templates like this:

    <ul>
        {#each items as item}
            <li>{item.message}</li>
        {/each}
    </ul>

Angular uses markup-based templates like this:

    <ul>
        <li *ngFor="let item of items">
            {{ item.message }}
        </li>
    </ul>

And let’s not forget that the world doesn’t begin and end with JavaScript. Most other templating systems are either markup-based or text-based. For instance, Jinja2 is text-based:

    <ul>
        {% for item in items %}
            <li>{{ item.message }}</li>
        {% endfor %}
    </ul>

JSX really isn’t that great. Sometimes it feels like most React devs don’t know how to write a for loop or if statement because they mostly use map(), ternaries, and short-circuiting, which are not very ergonomic compared with markup-based approaches.