Are We Turbo Yet?
summary
Claims that every build becomes incremental and that rebuild cost scales with the size of the change not the app, implemented as a Rust-based TurboAC reactive cache built from signal-like value cells and turbo functions, with SWC/Babel as transformers. The system exposes 2500 turbo functions and can spawn millions of tasks; on an 80,000-module production app cold builds hit ~94s with ~16s spent flushing the file cache, warm builds and fast refresh show roughly 3x improvements and Turbopack is now stable in Next 16.
AI-written summary · about
chapters (6)
- 0:00The need for speed
- 10:37Signals in Turbopack
- 16:00Trade-offs and consequences
- 20:12Large application performance
- 21:31Small application performance
- 23:19Turbopack is stable
related talks
10mTurbopack Rust Based Successor To Webpack
10mBuilding Infinitely Scalable Applications with Next.js and Turborepo
51mMoving at the Speed of Thought
33mScaling Swift Development
29m"High-Level Rust and the Future of Application Development"
11mPerformant Bazel Builds for Web Monorepos at Scale
30mModularization
26mArchitectural Changes In New V8 versions