XSLT is a cross-browser API for converting XML data into string or virtual DOM implemented natively with multithreaded streaming processing. Accounting the libraries for JSON to XML, extending XPATH with JS data access, and native XML support by XHR it gives native templating engine capable of holding and processing data volume on level of magnitude over JS based ones. The xml4jQuery library provides reactive asynchronous API for XSLT, XPATH, XML+JSON. By performance it stands right behind another native templating implementation: ES6 string literals.
Ranked in these QuestionsQuestion Ranking
Pro Permits pipelining
I.e. apply one template on top of another.
Pro AOP model
With ability to split feature implementation apart from main codebase, development became quite more manageable. Example: for data of particular type you could define own rendering or render refine rules; pipelining allows incrementally change UI by adding/removing elements depend of parameters, data values, previously rendered content.
Pro Native multithreaded implementation
Only template engine which utilizes multithreading.
Pro Native pre-compilation available
In some browsers(IE) XSLT during load is compiled into DLL. In others pre-loaded template allows to skip recurring parsing .
Pro Accept native data out of JS heap
XML when stored, saved outside of JS heap, capable to work with amount of data 100x larger of JSON.
Pro Native implementation
Supported in all browsers, starting from IE5.
Pro Server side rendering
XSLT is available as in browser as on server side via various libs including highly optimized for CPU.
Con Lack of SDLC for in-browser development
It will take time to collect complete gentleman set: debugging, modular development, documenting, unit tests, etc. Please share if know the book on subject.
Con Verbose syntax
Takes time to get used to.
Con AOP model
Is complex to comprehend, justifiable on complex projects.