Next. Js: Still Dominant...

- React 19 hit 48.4% daily usage among respondents within months of release, with SPAs still dominating at 84.5%. - Server Components are polarizing: adopted in 45% of new projects but explicitly cited as a pain point by 6% of developers. - TanStack is emerging as a cohesive client-first alternative to Next.js, with TanStack Query, Router, Start, and Form all gaining ground. ... Despite being used by 98% of respondents, `useEffect` has the lowest satisfaction ratio of any hook (State of React features). It was the number one complaint at 37%, followed by dependency array issues at 21% (a 23.5% increase year-over-year). Developers are vocal about the finicky reactivity model, stale closures, and effect cleanup issues. This is a feature that practically everyone uses and practically everyone struggles with. … ### Server Components: Polarizing Reception Server Components and Server Functions are the **third and fourth-most-disliked features**, respectively. The survey authors called this "troubling for a set of new APIs that was supposed to pave the way towards React's next big evolution." The negative sentiment stems from multiple directions: complexity, debugging difficulties, Context API incompatibility (59 mentions, the most significant hurdle), testing gaps (24 mentions), and the growing list of directives sparking debate. The December 2025 CVE-2025-55182, a critical remote code execution vulnerability affecting React Server Components, reminded developers that even production-stable APIs carry real-world security risks as the ecosystem continues to evolve (see also Microsoft's analysis). … ... Overall happiness averaged 3.6 out of 5 with a slight downward trend, though the survey cautions it's "far too early to conclude whether it's something to worry about or just a blip." Beyond hooks, ecosystem complexity was cited by 11% of developers. One respondent captured the frustration well: navigating competing state management solutions, routing libraries, and rapidly evolving metaframeworks has become an increasingly common source of friction. A structured content backend can reduce some of that complexity by decoupling your content layer from frontend architecture decisions. The top pain points reinforce each other. `useEffect` frustrations at 37%, dependency array issues at 21%, Server Component headaches at 6% (though notably, 45% of new projects adopted RSC, suggesting the pain is concentrated among active users). The ecosystem is healthy, but the pace of change and the client-versus-server divide create genuine fatigue. … ### Remix's Pivot