www.theregister.com
React survey shows TanStack gains - The Register
# React survey shows TanStack gains, doubts over server components ## Not everyone's convinced React belongs on the server as well as in the browser Devographics has published its State of React survey, with over 3,700 developers speaking out about what they love and hate in the fractured React ecosystem. React, originally sponsored by Meta, is a JavaScript library but not a complete framework, the result being that developers using React have a lot of choices when it comes to React-based frameworks and tools. The complexity of the ecosystem is a problem. "Getting a build and testing harness and CI system and IDE tools to all play nicely together is reliably a nightmare," complained one respondent. … React API top pain points according to the 2025 State of React survey. Note that forwardRef was deprecated in React 19 Next.js, which once looked set to become the standard choice for full-stack React, is widely used but not particularly beloved. Eighty percent of respondents have used it, but 17 percent have a negative sentiment, with most complaints focused on excessive complexity and too-tight integration with its main sponsor, hosting company Vercel. "Vendor lock in, complex APIs, and too much noise in the Next.js ecosystem make it a no-go for me," said one comment. Still, 27 percent ticked the box for positive sentiment, so opinion is divided.
Related Pain Points2件
React Ecosystem Fragmentation and Too Many Choices
6Developers face overwhelming fragmentation across state management (Redux, Zustand, Context), routing (React Router, etc.), server-side rendering (Next.js, alternatives), and other core concerns. 11% of developers specifically cited ecosystem complexity as a pain point, describing it as navigating competing solutions and rapidly evolving metaframeworks.
Framework perceived as overengineered for complexity added
5Many developers perceive Next.js as overengineered, adding unnecessary complexity without proportional benefits. The framework's architectural decisions and accumulated features create bloat that doesn't serve most use cases.