Let's address the "catching up to PHP" meme. What's different between @nextjs today and PHP? 1️⃣ Out-of-order streaming Notice how (app-router.vercel.app/stream…) we stream: ◆ a per-user shipping estimate ◆ per-user recommendations These end up in different parts of the UI, and can even be queried from multiple microservices. PHP's mechanism for streaming is very naive (linear) 2️⃣ Instant loads with Partial pre-rendering The static "stencil" of the page with CMS, non-personalized content (which you can still push updates to at runtime via ISR) can be extracted out at build time. This shell doesn't have to be output by the "php-fpm process". It can be hoisted externally, pushed to the edge and served statically. It gives a dynamic page the TTFB and performance or static. 3️⃣ Server and Client components React & JS can run in both server and client. Once you stream in the carousel, it can be very richly interactive, spin up a lightbox, etc. Modeling this complexity with PHP was extremely difficult. When Node.js came out I was one of the earliest users, and I wrote one of the first books, titling it "JavaScript everywhere" on the basis of achieving this universal runtime dream. amazon.com/Smashing-Node-js-…