This removes React as the potential cause of bottleneck, for example github.com/react-spring/zustand is similar. I guess this depends on your use case.
This optimization (and example) focusses less on State management and more on updating state. And updating state from different and more often unrelated parts of your app.
Yes this pattern can be good for that, I’ve used it in the past where I needed a component to react to the end of an animation from an unrelated component
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 removes React as the potential cause of bottleneck, for example github.com/react-spring/zustand is similar. I guess this depends on your use case.
This optimization (and example) focusses less on State management and more on updating state. And updating state from different and more often unrelated parts of your app.
Yes this pattern can be good for that, I’ve used it in the past where I needed a component to react to the end of an animation from an unrelated component