Why Do React Hooks Rely on Call Order?
overreacted.io
Why Do React Hooks Rely on Call Order?
1–10 of 115 posts
Re: Why Do React Hooks Rely on Call Order?
#2(I edited the post title to include “React” before the “Hooks” to disambiguate. Might be worth editing the submission too!)
Hope you’ll enjoy reading it.
Re: Why Do React Hooks Rely on Call Order?
#3The first two comment snippets read like someone who woke up with a horse's head in their bed after refusing the proposal from the React Family.
Re: Why Do React Hooks Rely on Call Order?
#4I’m surprised Reagent’s ratoms weren’t an inspiration. They give you a lot of Hooks functionality largely through Clojure’s native atom.
Re: Why Do React Hooks Rely on Call Order?
#5(I edited the post title to include “React” before the “Hooks” to disambiguate. Might be worth editing the submission too!) Hope you’ll enjoy reading it.
Just want to say that I've been loving your posts so far. Well written and I love the perspective of exploring _why_ an API is designed the way it is instead of trying to focus on explaining why is the best for . There are only a handful of blogs I've read over my career that I feel like focus on solving real application development problems, exploring trade-offs, or digging into why an approach was taken and these posts are of that caliber. Those topics help me in the problems I encounter frequently in my day job and make me a better engineer.
Thank you for the time and effort you're putting into this.
Re: Why Do React Hooks Rely on Call Order?
#6(I edited the post title to include “React” before the “Hooks” to disambiguate. Might be worth editing the submission too!) Hope you’ll enjoy reading it.
Thanks, this was fun. Enjoying your "unofficial" posts.
Re: Why Do React Hooks Rely on Call Order?
#7Beg to differ, yes, implicit call order will result in huge clusterfucks. React+Redux is already causing Frankenstein apps (which is not implicitly caused by those frameworks (ok, maybe except redux) but when you throw in react-redux, react-router, redux-thunk, etc. in the mix it just deteriorates quickly).
Well the NPM report showed us the trends. Every major fad peaks around 5 years in the making in JS land and then it fades away. We are halfway through. We just have to sit through the next 3-5 years.
Re: Why Do React Hooks Rely on Call Order?
#8Beg to differ, yes, implicit call order will result in huge clusterfucks. React+Redux is already causing Frankenstein apps (which is not implicitly caused by those frameworks (ok, maybe except redux) but when you throw in react-redux, react-router, redux-thunk, etc. in the mix it just deteriorates quickly). Well the NPM report showed us the trends. Every major fad peaks around 5 years in the making in JS land and the…
What way of structuring frontend prior to the react/redux 'fad' do you think was superior?
Re: Why Do React Hooks Rely on Call Order?
#9Beg to differ, yes, implicit call order will result in huge clusterfucks. React+Redux is already causing Frankenstein apps (which is not implicitly caused by those frameworks (ok, maybe except redux) but when you throw in react-redux, react-router, redux-thunk, etc. in the mix it just deteriorates quickly). Well the NPM report showed us the trends. Every major fad peaks around 5 years in the making in JS land and the…
On the contrary: Redux's insistence on serializable events and side effect-free reducers makes debugging these pernicious "state update" ordering issues, which exist with or without Redux, a far easier job.
Re: Why Do React Hooks Rely on Call Order?
#10Beg to differ, yes, implicit call order will result in huge clusterfucks. React+Redux is already causing Frankenstein apps (which is not implicitly caused by those frameworks (ok, maybe except redux) but when you throw in react-redux, react-router, redux-thunk, etc. in the mix it just deteriorates quickly). Well the NPM report showed us the trends. Every major fad peaks around 5 years in the making in JS land and the…
It's boilerplate rather then Frankenstein.