Re: [WICG/webcomponents] [templates] Ensure that template instantiation actually improves the platform (#704)

When it goes to speed of template rendering, think of
* rendering while data still load
* rendering while the template is still in progress of load.
I.e. both could (and for performance reasons should) be available via streaming and result available as stream as well. 

To be efficient the template could be tuned against **data schema**. Which would make generated code compiled up to binary level and processed in parallel threads.

Which goes back to beautiful concept of XML+XSLT 😛 

Now tell me that reasons above are not more significant than discussion ^^. Replace the XML/XPath/XSLT with equivalents supported by browser and you have #1 by performance and memory efficiency. From another hand what prevents to use XSLT as it is already part of browser stack?

* indirect JS data access, no streaming of JS-data
* syntax( with so many transformers around, we could change it at no time )
* lack of modular development ( same - transformer would solve it ) 
* no DOM binding/rendering directly into DOM ( same reason as discussed diffs for VDom ^^)

The polyfill could go only to certain level of performance for such design. Most heavy lifting would be on browser engine. But even streaming render in polyfill would beat React and similar VDOM rendering engines.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/issues/704#issuecomment-1195039857

You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/issues/704/1195039857@github.com>