JavaScript once had a JSX-like syntax called E4X (opens in new tab)

I've written an in depth blog post on "generic jsx", which turns JSX into function bind/currying syntax that would work fine in any framework (or not framework at all, as we currently use it).

http://tolmasky.com/2016/03/24/generalizing-jsx/

We use this generic-jsx in DemoKit: https://github.com/runkitdev/demokit , and it's really cool because you can do fancy stuff like:

      // Curry your JSX tags!
      const wordmark = <span style = "font-face:custom; font-weight:bold" />;

      .... <wordmark>hello</wordmark>

Perhaps providing a parser from something like the tagged template literals[1] from e.g. 'tag `string interpolation`' could be used. For ones lacking a tag, a specially named variable could be looked for (e.g. something like __xml_parser__ ) , it would be up to the program to set that global.

if would mean that jsx would look something like

    function helloEl() {return jsx <div> Hello ${name}! </div>}

as opposed to

    function helloEl() {return <div> Hello {name}! </div>}

It would be a bit different though in what is actually going on though. The top example would just desugar to

    jsx.div(`Hello ${name}`)

jsx would be looked up like any other variable. So you could just define it in global scope to point to ReactDOM

1: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...

You can already translate JSX to `document.createElement` with babel. I haven't seen one, but I wouldn't doubt a `customElements.define` translation is coming as well.

Could you specify the dom nodes that would be created and leave the API that JSX desugars to/calls into in order to create them unspecified?

Does syntax standardization have to necessarily equate to implantation standardization?

I quite loved my small stint developing in Adobe flex. I have to admit it.

You're thinking of MXML. Different thing.

It existed in AS3 too. Wasn't widely known to my knowledge though.

And the TU-Graz Hyper-G system => Hyperwave, which was very popular in the early internet days. It preceded WWW and Netscape by a bit.

> So far ahead of its' time

Or, JSX is so backward, behind its time?