Next.js Is Ditching the Static vs. Dynamic Split, Explains Aurora Scharf @CallstackEngineers
Next.js Is Ditching the Static vs. Dynamic Split, Explains Aurora Scharf  @CallstackEngineers
Uploaded December 2025 | Updated September 2026, 1 day ago
Next.js is changing how it handles rendering, moving away from the static vs. dynamic split. Aurora Scharff explains the new unified model that's coming.

Built on Server Components, this approach aims to simplify development and boost performance. The new model statically renders everything by default, you just suspend your dynamic content.

Aurora also covers how this will help developers who "struggle with where to put their suspense boundaries" by providing warnings for non-optimal patterns.

Follow Callstack on X 🐦 https://x.com/callstackio
Next.js Is Ditching the Static vs. Dynamic Split, Explains Aurora ScharfA (Secure) Christmas Carol: The Story of Npmezer ScroogeReact Strict DOM: Nicolas Gallagher on Writing Once for Web & NativeLive Dev Session: Rozenite DevTools Plugins, Precompiled React Native for iOS, TanStack DB 0.1Voltra: when React Native meets SwiftUIReact Native 0.83: No Breaking Changes, New DevTools and React 19.2 FeaturesLive Dev Session: Week 28 React & React Native RundownIs Your Project Setup Costing You Big Time?Understanding Threads and Queues in Swift TurboModulesWhere Reanimated Goes Next | Interview With Bartłomiej BłoniarzElevate React Native Observability With OpenTelemetry by David Rifkin | React Universe MeetupBuilding Node-API for React Native With Khalef Hosany & Kræn Hansen
Callstack |

Next.js Is Ditching the Static vs. Dynamic Split, Explains Aurora Scharf

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER