I'm gonna say it. Flux hampered React innovation: led everybody right back to events and "templates" and intimately knowing data changes.
-
-
I’m a bit confused about this conversation. I haven’t seen people implement sCU by hand except corner cases. Use shallow checks instead.
-
I'm also confused
@wycats. sCU pairs well with prop passing (and immutability ofc). But if you wormhole, subscribe at the destination. -
But the the ancestor sCU doesn't know about the descendent subscription.
-
Redux (or Flux) doesn't rely on this. Each component is notified independently (and can bail out). Parents don't know about children.
-
In React sCU only defines what happens to specific component. It doesn't decide for the whole subtree if child has sideways subscription.
-
An external subscription mechanism is definitely a hack though. It breaks how React behaves.
-
Yeah. I'm just musing in this thread, had we not side-stepped so quickly maybe there's an awesome react-like solution we're just not chasing
-
The Ember approach is to always *pull* data consistently so we can build sCU for you. May like it or not but it works and worth exploring.
- 2 more replies
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.