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

Hey @EisenbergEffect, thanks for taking the time. My issues were not about the specific syntax choice, but rather that it is a [square peg in a round hole](https://en.wikipedia.org/wiki/Square_peg_in_a_round_hole) situation. Of course with enough effort you can make anything work. But is it natural to do so? Wouldn't it be better to find a round peg?

I'm happy to dig more into the proposal if you'd like. I understand what it is doing. It's similar to [Alpine.js](https://alpinejs.dev/) (in approach, not syntax), in that you are writing a template within a template. Writing the same thing two times with different syntax. To take one of your examples, within your host language template you'd be writing something like: `<a href="./users/{{# user.id}} <%= user.id %> {{/}}">...</a>`, specifying the same logic in two different templates. Things like Alpine work ok in simple scenarios but break down as complexity grows; ie doing something like a loop with sorting is difficult. Personally I do not find this example to be something I'd desire to write.

How does one then perform an update in their host language? I don't think that it's really practically possible outside of the C# Blazor approach of compiling to wasm. Most other server language communities have not gone in this direction and instead are preferring a PRC + Diffing approach. We should look as to why these languages have not followed the pattern of this proposal.

Anything is possible with enough effort, but this thread is positing that a "binding from a distance" (hat-tip to @bahrus) approach is a better fit for the same reasons that CSS is a better fit than `<font>`, `<center>` and friends.

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

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