Hacker News new | past | comments | ask | show | jobs | submit login

As a contrary opinion, I find Redux simplifies my react projects by virtue of having a standardized set of practices for handling state. The flux pattern in general is amazing, and I always wrote spaghetti, passing props everywhere, prior to discovering it.



After I switched to a 3 layer architecture (1. root component, 2. screen components, 3. ui components) I just had to gather data asynchronously in the screens and pass it into the UIs via props and that was it. No spaghetti, no Actions/Reducers.

I'm not saying this works for all apps, but I got pretty far with it.


3-tier on the client :)


Do you have an example somewhere on-line? I'm also not familiar with the term "screen components"


On mobile apps, the "pages" are called "screens" it's just the main UI container that gets replaced if you switch between screens


Ah, that makes sense. Thanks!




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: