News AI
July 19th, 2024

State of React survey results

React, a leading web development library, has evolved with innovations like Server Components and a Compiler. The unofficial State of React survey offers insights into component libraries and application trends, showcasing React's adaptability and leadership.

Read original articleLink Icon
State of React survey results

React, a prominent web development library, has been evolving over its 11-year existence to meet user demands. The latest innovations include Server Components and an upcoming Compiler. The State of React community survey conducted between October 27 and November 15, 2023, offers insights into component libraries, state management, and application patterns. Notably, the survey is unofficial and not associated with Meta, Vercel, or the React team. The survey results provide a comprehensive overview of React's current landscape, showcasing its adaptability and leadership in the web development domain. Despite the survey's limitations in covering developments post-November 2023, it remains a valuable resource for understanding React's status and trends within the community.

Related

Link Icon 4 comments
By @pjmlp - 3 months
For 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.

By @meiraleal - 3 months
State of React: dying a slow death
By @SebastianKra - 3 months
I'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.