This is soooo true. Almost all of the frontend problems I run into are state management. Like "Do I have this data yet? If I don't have the data yet, what should the UI do? When I get the data, what needs to change? What happens if a user types in this field or clicks this button? What changes do I need to make to get the data in the right shape to work with these two different places."
The days of static websites are long gone, which is why people complain about the complexity of JS tooling. Most of that tooling is there to help with asynchronous state management (which is a "hard" problem). I think it's natural that as people expect more interactive websites we'd end up with more state management as a consequence.
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.
This is soooo true. Almost all of the frontend problems I run into are state management. Like "Do I have this data yet? If I don't have the data yet, what should the UI do? When I get the data, what needs to change? What happens if a user types in this field or clicks this button? What changes do I need to make to get the data in the right shape to work with these two different places."
The days of static websites are long gone, which is why people complain about the complexity of JS tooling. Most of that tooling is there to help with asynchronous state management (which is a "hard" problem). I think it's natural that as people expect more interactive websites we'd end up with more state management as a consequence.