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

titoBouzout left a comment (WICG/webcomponents#1069)

Downsides:

- not able to set a namespace, say to create a partial that goes inside SVG/MathML
- returns an obscure object so we have to add yet another instanceof
- shortsighted about how stuff should be updated, as in, not just because you pass a signal that would be the end result, the signal could return another signal/promise, any other thing that has some custom render. And on this from where the effect comes from?
- what about async values?
- the conditionals and loops leave much to be desired, a simple map won't suffice
- doesnt seem to be clear whats going to be escaped and what's going to be evaluated, for when you have some string with html that want to be rendered
- It doesnt seem to support markedup-components as functions, else we will end with a string full of interpolations
- it has the html whitespace problem thats hard to deal with 
- makes the browser even more complex for no reason
- DOM proposals are being misused to add all this fantasy high level stuff when what should be worked on is all the much-needed low level things 

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

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