Re: [WICG/webcomponents] [templates] A declarative JavaScript templating API (Issue #1069)

Immediate questions I have:

* How does this integrate with signals?
* Can fine-grained updates be accomplished or is re-rendering required?
* How do we expect a server DSD version to be generated? How do we expect it to resume on the client?
* Can we have an in-HTML equivalent that doesn't require JS? Pretty please.

These days, I'm highly focused on declarative patterns that don't require JS for initial render. I know we want to move the ball forward for templating, but I'd still prefer to move it forward on the HTML side rather than in JS. For most of the clients I'm consulting with, this will not help their key scenarios at all. More progress on declarative approaches is what they need.

---

Note that in FAST, things work a good bit differently, even though the tagged template literal part looks the same. In FAST, state is backed by signals and bindings are live. So, there is no re-render step. Rather, when a signal value changes, FAST makes a fine-grained update to precisely the DOM node that has changed (batched with any other changes that happened in the same micro task).


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

Message ID: <WICG/webcomponents/issues/1069/2293915115@github.com>