As per your first point, if you ever needed to delay a setState and then use the new value in the same call stack, you know it's not possible only using the state. Having to use a state + a ref for this situation is just a hack, and I didn't want that. The stale state problem isn't part of React philosophy, it's just a necessary evil.
As per the proxy implementation, I never liked the "setState" function mechanism, I wanted something TRULY reactive. This also answers about your rewrite.
The observer pattern (sub/unsub) is a mechanism that can be very useful for certain use cases, first of all if you need to do something BEFORE React rerenders the component. What if you need to update a second state when the atom updates? A useEffect would need 2 rerenders, 1 for the first state and 1 for the second one, by using the atom you only have 1 rerender instead.
Another important difference in my implementation is the "previousValue", which isn't available in the useState hook.
You brought some good points on the table and I'd love to know if my comment answered your questions and convinced you or if you still have some doubts, I love meaningful discussion.
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.
As per your first point, if you ever needed to delay a setState and then use the new value in the same call stack, you know it's not possible only using the state. Having to use a state + a ref for this situation is just a hack, and I didn't want that. The stale state problem isn't part of React philosophy, it's just a necessary evil.
As per the proxy implementation, I never liked the "setState" function mechanism, I wanted something TRULY reactive. This also answers about your rewrite.
The observer pattern (sub/unsub) is a mechanism that can be very useful for certain use cases, first of all if you need to do something BEFORE React rerenders the component. What if you need to update a second state when the atom updates? A useEffect would need 2 rerenders, 1 for the first state and 1 for the second one, by using the atom you only have 1 rerender instead.
Another important difference in my implementation is the "previousValue", which isn't available in the useState hook.
You brought some good points on the table and I'd love to know if my comment answered your questions and convinced you or if you still have some doubts, I love meaningful discussion.