Re: [w3c/webcomponents] [templates] If HTML Template Instantiation proposal is adopted, consider a HTML-native syntax (#695)

I know this thread is closed, but was interesting.

After reading through Apples proposal and the ideas on this thread, my conclusion is XSLT. We have an XSLT processor in the browser already, it's functional and more powerful beyond what we could reinvent. I think the new devs who have never used XSLT, just didn't consider it (?). User passes a JSON {} to template which receives it as serialized XML. From there, XSLT syntax. There is a performance hit i can imagine, but we won't do this when building a game and having to update thousands of sprites, but better employed to render 1 off tables and grids, (plus we paginate, never thousands of rows) article-type content, custom order-like screens or forms. These are less cpu intensive.


The other idea is what we already have, template literals. I don't have to explain this.

3rd, use a templating api like so many of them out there.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/695#issuecomment-538737197