[ajxs]

The core concept behind XSLT is evergreen: Being able to programmatically transform the results of a HTTP request into a document with native tools is still useful. I don't foresee any equivalent native framework for styling JSON ever coming into being though.

[_heimdall]

If I'm not mistaken, XSLT 3 works with JSON too. It'd be nice to see that shipped in browsers instead of seeing v1 removed.

[stmw]

I could easily imagine a functional-programming JSON transformation language, or perhaps even a JSLT based on latest XSLT spec. The key in these things is to constraing what is can do.

[ajxs]

We wouldn't even need anything as complex as XSLT, or a functional language for transforming JSON. Other markup-based template processing systems exist for higher-level languages like Pug, Mustache, etc. for Node.js. You could achieve a lot with a template engine in the browser!

[b_e_n_t_o_n]

JSX!

[stmw]

That's not... really the same.

[mpyne]

> I don't foresee any equivalent native framework for styling JSON ever coming into being though.

Well yeah I hope not! That's what a programming language is for, to turn data into documents.

[asteroidburger]

XSLT 2.0 is Turing complete.

[mpyne]

So are many esoteric languages, but I doubt people would appreciate me comparing XSLT to Brainfuck or FORTRAN 66.

[stuaxo]

Having something declarative is good here, and XSL fills that.

[nashashmi]

Let’s rewrite W3C into XML and xslt.