@wycats @floydophone @tomdale It lets you think about building pages just like you do on the server, with all the data at once.
@mjackson @floydophone @fivetanley @tomdale don't see why the observable approach can't reuse DOM nodes.
-
-
@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. -
@mjackson@floydophone@fivetanley@tomdale our current lib impl reuses nodes far too infrequently but not fundamental. Improving. -
@wycats Can the user decide when to reuse vs destroy/create?@mjackson@fivetanley@tomdale -
@floydophone@mjackson indicated he wants the lib to decide for him.@fivetanley@tomdale -
@wycats@floydophone@fivetanley@tomdale And I think it should default to reusing as much as possible. Make me work to have it otherwise. -
@mjackson@floydophone@fivetanley@tomdale agreed that the selection state, scroll pos and focus are under appreciated.
End of conversation
New conversation -
-
-
@wycats@floydophone@fivetanley@tomdale This is why I'm saying the lib can't be ignored. The thinking is sound, but the lib supports it.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@wycats This is another thing to pay attention in react-the-implementation, not react-the-architecture@mjackson@fivetanley@tomdale -
@floydophone@mjackson@fivetanley@tomdale agreed. Sounds like there are impl areas where React does good work.
End of conversation
New conversation -
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.