Earlier quoted context omitted.
In my experience React codebases turn into this mess for two reasons: - front-end devs don't know how to think declaratively and think in terms of state transitions instead of realizing intent - back-end devs build a classic REST-like API which provides zero affordances to drive a proper reactive front-end. React-query is a good solution to the wrong problem. It's basically an elaborate and ornate footgun that allows…
> front-end devs don't know how to think declaratively and think in terms of state transitions instead of realizing intent There is a thing among park rangers where “if people are taking this shortcut despite the signs and fences, then it’s the trail that’s wrong, not the people”. More software engs should think this way instead of “educating harder should solve incompetence”. It’s not that people are incompetent. Th…
React chaos in mid and large web apps: Any different experiences?
51–52 of 52 posts
Re: React chaos in mid and large web apps: Any different experiences?
#52Earlier quoted context omitted.
In my experience React codebases turn into this mess for two reasons: - front-end devs don't know how to think declaratively and think in terms of state transitions instead of realizing intent - back-end devs build a classic REST-like API which provides zero affordances to drive a proper reactive front-end. React-query is a good solution to the wrong problem. It's basically an elaborate and ornate footgun that allows…
> front-end devs don't know how to think declaratively and think in terms of state transitions instead of realizing intent There is a thing among park rangers where “if people are taking this shortcut despite the signs and fences, then it’s the trail that’s wrong, not the people”. More software engs should think this way instead of “educating harder should solve incompetence”. It’s not that people are incompetent. Th…
Yes, the problem is the devs. They don't even understand how applications work.