Re: [WICG/webcomponents] DOM parts use outside of <template> seems unlikely (Issue #1035)

@tbondwilkinson 

> How do non-JS frameworks handle interactivity - there's still some JS that does that, or am I missing the point?

Let me clarify something that I think I haven't articulated well in this thread. My opposition to the current proposal is this:

1. The templating proposal is helpful for those following an "isomorphic" architecture. (particularly if we include the `parseparts` part).
2. Isomorphic architecture is really only possible in JS backends.
3. Therefore, this proposal is only helpful to a subset of applications.
4. Furthermore, this proposal is big and will take a long time and a lot of resources to see through. It will be seen as "the way" going forward and make it more difficult for alternatives to ever happen.

----

My counter-proposal is not attempting to solve the problem of "isomorphic" architecture. It is instead looking for another way to achieve the same underlying goals that we all want; a way to do declarative DOM updates, and it is trying to do so in a way that is decoupled from the backend.



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

Message ID: <WICG/webcomponents/issues/1035/1808738052@github.com>