State of React survey results
2023.stateofreact.com
State of React survey results
1–6 of 6 posts
Re: State of React survey results
#2For me, the only thing that matters is that plenty of SaaS CMS products nowadays are only having Next.js and React based SDKs, so whatever one thinks about them, they are the ones one gets to use, when customers have such products deployed.
Unless one enjoys explaining customers why they went with a DIY solution instead of using the products SDKs.
Re: State of React survey results
#3I'm disappointed to see Zustand winning in sentiment over Redux (Toolkit).
I tried to use it for a moderately complex table-editor and quickly ran into scaling problems that, IMO, the authors should have anticipated: confusing Typescript errors, excessive nesting (partially because each middleware must wrap the entire store), name-spacing (aka slices) is basically not supported...
I wonder what other devs use it for, that's simple enough to not run into these problems yet too complex for useState/useReducer.
Re: State of React survey results
#4State of React: dying a slow death
Re: State of React survey results
#5[flagged]
Re: State of React survey results
#6I'm disappointed to see Zustand winning in sentiment over Redux (Toolkit). I tried to use it for a moderately complex table-editor and quickly ran into scaling problems that, IMO, the authors should have anticipated: confusing Typescript errors, excessive nesting (partially because each middleware must wrap the entire store), name-spacing (aka slices) is basically not supported... I wonder what other devs use it for,…
MobX and chill.