Application Architecture with React: Rethinking Flux

Re:Application Architecture with React: Rethinking Flux by bpicolo on Monday September 14, 2015 @11:12AM (#10215433)

I feel like every new architecture for flux lately comes at the cost of a lot of code complexity. The global state is becoming extremely common too, and it feels like a big anti-pattern. Not really a fan. I do like the more pure-flux Alt at the moment. I felt quickly put off from Redux after going through docs for a while.

[ Parent | on HN ]

Re:Application Architecture with React: Rethinking Flux by iLoch on Monday September 14, 2015 @11:47AM (#10215634)

Only the states that can be global need to be global. It's not an anti pattern to manage state inside the component.

[ Parent | on HN ]

Re:Application Architecture with React: Rethinking Flux by dustingetz on Monday September 14, 2015 @11:15AM (#10215461)

databases are global state

(The design pattern here is separation of code from state. OOP couples code (methods) and state (members))

[ Parent | on HN ]

Re:Application Architecture with React: Rethinking Flux by bpicolo on Monday September 14, 2015 @11:56AM (#10215688)

I realize that about databases, yes. I think the particular ways that frameworks have been trying to handle state are bad patterns. Not sure what would be better at the moment, but currently it's a mess.

[ Parent | on HN ]