State Of JS 2023

JavaScript fatigue is rising, and the ecosystem’s churn is being blamed for a broad drop in developer happiness—especially around front-end frameworks and meta-frameworks. While JavaScript itself remains central, the surrounding tooling and competing approaches (server-first patterns, new framework features, and constant library churn) are pushing many developers toward “concave down” frustration: adoption continues, but sentiment and satisfaction slide over time.

A major through-line is that the web’s pace is outstripping developers’ ability to keep up. The discussion ties this to “not invented here” (NIH) syndrome—teams repeatedly rebuilding their own solutions when something doesn’t fit—leading to fragmentation across standards, libraries, and frameworks. That fragmentation shows up in the survey’s emphasis on how quickly new innovations arrive, from server components and server actions to signals, compilers, and other ecosystem shifts. The proposed antidote is “pick your lane”: adopt cutting-edge tech selectively, but prioritize stable, mature options until the ecosystem cools.

The survey results also highlight a shift in where attention is going. Server-rendered and server-first patterns are gaining ground: partial hydration and island-style approaches doubled in adoption, reflecting a broader move toward running more logic on the server. React remains dominant, but react developers increasingly worry about direction and complexity. Outside the React orbit, adoption is spreading to frameworks and libraries such as Nu to solid starts to Astro, with Astro portrayed as “off to the races” in interest and growth.

Tooling sentiment is similarly mixed. Vite stands out as a consistent bright spot—high adoption, strong retention, and positive sentiment—while older or more complex tools trend toward frustration. Webpack remains widely used but is repeatedly associated with pain points like configuration overhead and monorepo-related build-tool complexity. Testing tools show a similar pattern: Jasmine and Vitest appear comparatively healthier, while legacy tools like Mocha retain usage but struggle with retention and positivity. Across the board, performance, excessive complexity, state management difficulty, and debugging friction recur as the most common pain points.

The transcript also surfaces a meta-framework “happiness gap.” Next.js dominates usage and interest, but negative sentiment around it is framed as a predictable byproduct of scale: the more widely used a tool becomes, the more likely developers are to encounter edge cases, workflow friction, and feature bloat. Astro, by contrast, is described as having fewer negative experiences among those who use it, suggesting a different adoption curve—less “everyone is forced to use it” and more “opt-in for a specific style.”

Finally, the discussion broadens beyond front-end. Mobile and desktop tooling show uneven sentiment, with Electron still prominent and native-app approaches rising. On the backend and runtime side, Express and other server frameworks remain common, while JavaScript’s role is framed as unavoidable across domains—though developers still describe it as painful at large scale. The overall takeaway: the ecosystem is moving fast, server-first patterns are accelerating, Vite is the standout, and developer happiness is sliding as complexity compounds—especially in the frameworks and build systems that many teams rely on every day.