The problems OP tries to address are unfortunately a deep design flaw in mainstream frameworks like React and Vue. This is due to 2 properties they have: 1. They marry view hierarchy to state hierarchy 2. They make it very ergonomic to put state in components I've been through this endless times. There are significant ways to reduce this friction, but in the end there's a tight ceiling. This is why this kind of work…
Vue provides a computed feature that acts as a buffer layer between the view and the state, so the view and the state are not necessarily strictly bound
Show HN: Tired of logic in useEffect, I built a class-based React state manager
51–57 of 57 posts
Re: Show HN: Tired of logic in useEffect, I built a class-based React state manager
#52Re: Show HN: Tired of logic in useEffect, I built a class-based React state manager
#53Re: Show HN: Tired of logic in useEffect, I built a class-based React state manager
#54Re: Show HN: Tired of logic in useEffect, I built a class-based React state manager
#55Earlier quoted context omitted.
You can lead a horse to water...
I have been drinking water for years. You are trying to tell me water is an antipattern and I should drink gatorade instead. No thanks.
Did you even read the article I linked? If not, please do. If you did read it, and still believe it makes no difference, I can't do anything more to help and will simply wish you good luck and have a nice day.
Re: Show HN: Tired of logic in useEffect, I built a class-based React state manager
#56Earlier quoted context omitted.
I have been drinking water for years. You are trying to tell me water is an antipattern and I should drink gatorade instead. No thanks.
I'm doing no such thing. I'm alerting you to the fact that the owner of the well where you've been drinking has warned that it's not potable and suggested drinking the pure, filtered water instead. Did you even read the article I linked? If not, please do. If you did read it, and still believe it makes no difference, I can't do anything more to help and will simply wish you good luck and have a nice day.
I did read the article linked. I am remain unconvinced. Use effect for data fetching is not "risky", "fragile", and does not cause "subtle, hard to debug problems". This is baseless fear mongering. Claiming Tanstack is the "right" way is incredibly arrogant.