3 ms·
themgt posted the following on the currently trending React thread, sharing what appears to be Flux's impending sunset: One of the things I didn't realize at f
by j_s 12y ago
themgt posted the following on the currently trending React thread, sharing what appears to be Flux's impending sunset:
One of the things I didn't realize at first was the degree to which Relay/GraphQL appear to effectively replace a lot of Flux: http://facebook.github.io/react/blog/2015/02/20/introducing-relay-and-graphql.html http://facebook.github.io/react/blog/2015/02/20/introducing-...
Learning Flux sort of seems like learning how to drive stick shift on an '97 Civic while we wait for the new Tesla to arrive - useful, also a bit annoying. A central store architecture does seem a better match to what Relay will look like though.
https://news.ycombinator.com/item?id=9094255 https://news.ycombinator.com/item?id=9094255
edit: fixed link; thanks!
- mrec 12y agoLooks like that first link got truncated to the ellipsized display form when you copypasted; full one should be; http://facebook.github.io/react/blog/2015/02/20/introducing-relay-and-graphql.html http://facebook.github.io/react/blog/2015/02/20/introducing-...
- vmind 12y agoRelay looks like it will partially replace Flux if you're using it to manage the client<->server state, but Flux still seems necessary if you have a lot of intra-client state to manage (such as in a document-editing SPA).