I like to keep conditionals and loops in real js whenever possible. Turns out there is already a syntax for both! :)
-
-
Replying to @stubbornella @wycats and
One of the benefits to having templates in the js is that you write more real js and less magic... imo
3 replies 0 retweets 5 likes -
Replying to @stubbornella @youyuxi and
Fair enough. I think you might be undercounting the cognitive costs to some in mixed JS/XML but again YMMV.
1 reply 0 retweets 1 like -
Replying to @wycats @stubbornella and
I think the level of adoption speaks for itself.
1 reply 0 retweets 1 like -
Replying to @HenrikJoreteg @stubbornella and
Handlebars is extremely popular too. As I said, different strokes for different folks.
1 reply 0 retweets 4 likes -
Replying to @wycats @HenrikJoreteg and
Overall I agree that template syntax is indifferent. The browser providing a way to dynamically merge two DOM trees is the primitive we need
4 replies 0 retweets 10 likes -
That's how i see it as well. No talk of templates or vdom, and yet it helps both.
1 reply 0 retweets 2 likes -
"dynamically merge two DOM trees" is very connected to VDOM diffing as a mechanic and completely unhelpful to Glimmer.
1 reply 0 retweets 1 like -
this conversation reminds me of MDV https://github.com/toolkitchen/mdv/blob/stable/README.md … I think there are multiple concerns in the problem space
1 reply 0 retweets 0 likes -
And adding a merge based API won't solve all the problems... It would be helpful to enumerate concerns in a doc....
2 replies 0 retweets 2 likes
Agree. I think there are lower level things that vdom approaches can target that we should do first. My first pass:https://github.com/whatwg/dom/issues/270 …
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.