Can confirm. This makes it a nonstarter for Glimmer too. VDOM is an implementation detail not a programming model.
-
-
Replying to @wycats @justinfagnani and
Could the diffing primitive could be used in bytecode vm that glimmer uses?
1 reply 0 retweets 0 likes -
Replying to @TheLarkInn @wycats and
The reason bytecode is useful is because it is more specific than diffing. If you have to diff anyway you’ve lost benefits of bytecode.
1 reply 0 retweets 9 likes -
Replying to @dan_abramov @TheLarkInn and
Right. We have an update program we run that avoids the need to ever diff except at the string level (attribute value, text node)
1 reply 0 retweets 6 likes -
Replying to @wycats @dan_abramov and
That's what I've been experimenting on too in regards to React. Admittedly it's way harder to do with React, as we have to evaluate raw JS.
1 reply 0 retweets 2 likes -
Replying to @trueadm @dan_abramov and
It's worth exploring in react but much harder to get right because it's hard to enforce restrictions in "just js"
2 replies 0 retweets 3 likes -
Not really... template literals just do that for you
1 reply 0 retweets 0 likes -
Replying to @justinfagnani @trueadm and
JSX is not the same thing as template literals. And stitching together JS loops / conditionals with templates also doesn't work.
3 replies 0 retweets 2 likes -
Replying to @wycats @justinfagnani and
let items = http://list.map (item => jsx`<li>${item}</li>`); return jsx`<ul>${items}</ul>`
1 reply 0 retweets 1 like -
Replying to @wycats @justinfagnani and
This is the sort of very simple thing people do all the time and like as "just JS" that starts to make it hard to do this optimization.
2 replies 0 retweets 1 like
And pushes them into a VDOM + diff approach with value type optimizations.
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.