The Great React Backlash: Growing Pains in the Frontend World

The developer community is witnessing an unusual phenomenon: a growing, vocal backlash against React, the once-unquestioned king of frontend frameworks. What began as niche criticism has now evolved into a substantial chorus of experienced developers, tech leads, and even entire organizations questioning React's dominance and suitability for modern web applications.

The Performance Conundrum

At the heart of much React criticism lies a persistent concern about performance. "In reality, for any decently sized JS-heavy project, you should expect that what you build will be slower than advertised, it will keep getting slower over time while it sees ongoing work, and it will take more effort to develop and especially to maintain than what you were led to believe," writes one developer with years of React experience.

The mobile performance concerns are particularly telling. "React's mobile strategy inherently drives teams toward platform capture. The web offers an alternative: no gatekeepers, no platform fees, direct distribution," notes another perspective, highlighting how React's approach may be at odds with the fundamental principles of the web.

One team's experience is particularly illustrative: "One dev team made the shift from React's 'overwhelming VDOM' to modern DOM APIs. They immediately saw speed and interaction improvements."

Security Vulnerabilities and Governance Issues

The recent security disclosure around React Server Components has added fuel to the fire. "On November 29th, Lachlan Davidson reported a security vulnerability in React that allows unauthenticated remote code execution," explains one security-focused post. "This vulnerability was disclosed as CVE-2025-55182 and is rated CVSS 10.0."

But the security concerns extend beyond the technical issues to governance, particularly around Next.js. "Vercel has become a Vercel vendor lock-in disguised as an open-source framework," argues one critic. "Save yourself the headache and choose something else for your 'next' project."

The handling of security vulnerabilities has drawn particular ire. "Last weekend, Vercel disclosed a critical security vulnerability with Next.js. This type of issue is normal, but the way Vercel chose to handle it was so poor, reckless and disrespectful to the community that it has exacerbated my concerns about the governance of the project."

The Complexity Crisis

Perhaps the most common thread in React criticism is the growing complexity that many developers feel has been baked into the framework's DNA. "React's core failure is compounded by confusing API design for which documentation is indecisive, essays are written, and correct usage is endlessly debated."

The developer experience has become a significant pain point. "React proponents might claim that React will teach you modern UI, but from what I've seen it barely copes with modern UI. autofocus is broken, custom elements don't work in all but the experimental version, using any 'modern' features like dialog or popovers requires useEffect, and the synthetic event system teaches you so little about how DOM actually works."

This complexity is creating a talent gap. "Several CTOs mentioned a surprising problem: while React developers are plentiful, truly skilled ones who understand the deeper patterns are increasingly rare and expensive," reports one observer. "Several companies reported that their most experienced engineers were getting frustrated with the growing complexity and leaving for roles using other technologies."

The Default Choice Problem

A fundamental criticism leveled at React is that it often wins by default rather than merit. "When teams need a new frontend, the conversation rarely starts with 'What are the constraints and which tool best fits them?' It often starts with 'Let's use React; everyone knows React.' That reflex creates a self-perpetuating cycle where network effects, rather than technical fit, decide architecture."

This default selection process is stifling innovation. "React Won by Default – And It's Killing Frontend Innovation," declares one headline, suggesting that the framework's dominance is preventing the exploration of alternative approaches that might better serve different use cases.

The criticism extends to how React is positioned to newcomers. "If you're a new web developer entering the profession, you might even consider eschewing React altogether – although admittedly, that will diminish your short-term job prospects. But it's at least an option to seriously consider, and might even help you land a job with a forward-thinking employer."

Alternative Approaches and Frameworks

The criticism hasn't been without proposed alternatives. Svelte has emerged as a frequent contender. "I've seen all those headlines about Svelte being the 'most loved' framework, and… well I admit, I just ignored it as noise. But the next time that survey comes around, I'll be right up there with them, waving from the Svelte bandwagon," writes one convert.

The practical benefits of some alternatives are compelling. "We Rewrote our React App in Svelte in Three Weeks," reports another developer, highlighting the potential productivity and performance gains.

Other approaches are gaining traction as well. "Replacing React: How Liveview solved our performance problems" describes how "Performance challenges with a React SPA created an opportunity to explore Liveview. After two days of exploration, we were convinced Liveview provided a path forward, and within a few weeks, we replaced our React SPA with Liveview."

The HTML-first approach is also seeing renewed interest. "HTML is better than React!? [...] baseline HTML that gets progressively enhanced into something better when JS is available… 1. Gives people a more usable experience earlier in the process. 2. Ensures that on slow connections your site doesn't seem like trash. 3. Means that if something goes wrong, people can still use your site."

The Counter-Perspective

Despite the growing criticism, it's important to note that React remains incredibly popular and widely used. The framework has solved significant problems for many organizations and continues to power countless applications successfully.

"React has its place, I'm sure, but it has turned into the proverbial hammer that makes everything look like a nail," acknowledges one critic, implicitly recognizing that React might be appropriate for certain use cases.

Others point to the ecosystem's maturity and the availability of talent as reasons React continues to dominate. "React developers are plentiful," notes one CTO, suggesting that the availability of developers who can work with the framework remains a significant factor in its continued adoption.

The React team's responsiveness to criticism should also be acknowledged. "After a lot of public pushback, heated discussions, and probably a good deal of talking behind the scenes, the React team backed out and decided to hold off on this change for now," reports one observer regarding React 19, suggesting that the team does listen to community feedback.

The Path Forward

The criticism of React reflects broader tensions in the frontend development ecosystem. The debate touches on fundamental questions about the trade-offs between developer experience and user experience, between abstraction and control, and between the convenience of frameworks and the principles of the web platform.

"The React community is mired in a deep, measurable quality crisis," observes one commentator, but also notes that this criticism is often absent from industry conferences, creating a disconnect between community sentiment and industry discourse.

As the ecosystem continues to evolve, the growing criticism of React may ultimately benefit all developers by encouraging more thoughtful technology choices, better tooling, and a renewed focus on web fundamentals. "By ejecting from the thrash of React and other heavy-handed frameworks and doubling down on web fundamentals, you'll be future-proofing both your career and your codebases," suggests one advocate for a return to basics.

The conversation around React's future is far from over, but it has undeniably shifted from one of unquestioned dominance to one of critical examination. In a rapidly evolving frontend landscape, this scrutiny may ultimately prove healthy for the entire ecosystem.