Yes. In my experience, useState / useEffect should be reserved for ui state only. Your application state (and general domain logic) should be kept as far away from your presentation layer as possible.
The crazy thing is, we'd developed all of these practices when redux was king. When hooks arrived, we abandoned everything and started throwing state everywhere, and now we're having to re-learn how to write sensible application state again.
When hooks arrived, we abandoned everything and started throwing state everywhere
I agree with this so much. I never really realized how disorganized my projects were becoming until I started to handle high profile ones that had relatively complex data structures and streams of data to take care of.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Yes. In my experience,
useState/useEffectshould be reserved for ui state only. Your application state (and general domain logic) should be kept as far away from your presentation layer as possible.The crazy thing is, we'd developed all of these practices when redux was king. When hooks arrived, we abandoned everything and started throwing state everywhere, and now we're having to re-learn how to write sensible application state again.
I agree with this so much. I never really realized how disorganized my projects were becoming until I started to handle high profile ones that had relatively complex data structures and streams of data to take care of.