@mjackson @floydophone @fivetanley @tomdale don't see why the observable approach can't reuse DOM nodes.
-
-
Replying to @wycats
@wycats@floydophone@fivetanley@tomdale Seems like it would need to be built in to {{#each}}. In any case, the lib should do it not me.1 reply 0 retweets 1 like -
Replying to @mjackson
@mjackson@floydophone@fivetanley@tomdale our current lib impl reuses nodes far too infrequently but not fundamental. Improving.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats Can the user decide when to reuse vs destroy/create?@mjackson@fivetanley@tomdale1 reply 0 retweets 0 likes -
Replying to @floydophone
@floydophone@mjackson indicated he wants the lib to decide for him.@fivetanley@tomdale2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats the lib cannot do that. it is essential complexity. it can provide a sane default though.@mjackson@fivetanley@tomdale1 reply 0 retweets 0 likes -
Replying to @floydophone
@floydophone@mjackson@fivetanley@tomdale when is destroying better and how should the user decide?2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats We pulled a page out of the d3 playbook http://facebook.github.io/react/docs/reconciliation.html#list-wise-diff …@mjackson@fivetanley@tomdale2 replies 0 retweets 8 likes -
Replying to @floydophone
@floydophone@mjackson@fivetanley@tomdale I should probably get back to work. Thought provoking discussion.2 replies 0 retweets 2 likes -
Replying to @wycats
Thanks
@wycats. Always appreciate your perspective.@floydophone@fivetanley@tomdale2 replies 0 retweets 0 likes
@mjackson @floydophone @fivetanley if you learn anything about me, it's that I don't stand still. I don't assume I have perfect answer
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.