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

Ah. I clean forgot one more thing. This proposal lacks a simple cost-benefit analysis. 

The proposal lists 9 use cases and provides satisfactory solutions to at most one or two if them. 

And despite this fact, and despite the fact there’s an ongoing debate around implementation of conditionals and loops, etc. etc. of course Chrome is already implementing it. 

Because who wouldn’t want another half-baked underspecified vague standard in the browser around which everyone will be busy building new workarounds and abstractions (because its nigh unusable otherwise). 

-- 
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/704#issuecomment-489560924