Next.js Rebuilt in a Week: When Speed Running Framework Development Actually Works

Someone rebuilt Next.js in a week. Not a toy version. Not a proof of concept. A legitimate reimplementation that actually compiles and runs. Meanwhile, React just got a literal foundation with $1M in funding, and Hermes (yes, the React Native JS engine) is now running in Node.js. This week proved that JavaScript moves different. Let's start with the Next.js speed run. Building a framework in seven days sounds unhinged until you realise what it actually demonstrates: Next.js isn't magic, it's just really good product decisions stacked on top of React. The rebuild stripped away years of enterprise feature bloat and revealed the core that actually matters. Routing, data fetching, and SSR. That's it. Everything else is negotiable. This matters because we've spent years treating frameworks like black boxes. "Don't look inside Next.js, just use it." But when someone casually rebuilds your entire framework over a long weekend, it forces a reckoning. Maybe these tools aren't as complex as we thought. Maybe we've been cargo culting complexity. Then React gets a foundation. Actual legal structure, actual funding, actual governance that isn't just Meta making unilateral decisions. This should have happened five years ago, but better late than never. The $1M seed funding is almost irrelevant compared to what this signals: React is becoming infrastructure, not just a library that happens to run half the internet. And Hermes in Node.js is the wildcard nobody saw coming. We've been so focused on Bun and Deno eating Node's lunch that we forgot about the mobile JS engine that's been quietly optimising for constrained environments. Hermes was built for React Native, optimised for startup time and memory usage. Exactly what serverless needs. Exactly what edge computing needs. Here's the pattern: JavaScript tooling is entering its speed running era. Rebuilding frameworks in a week. Porting engines between runtimes. Creating foundations for decade old projects. We're not innovating slower, we're innovating faster by understanding what actually matters. The Next.js rebuild proves the concepts work. The React foundation proves the ecosystem is maturing. Hermes in Node proves we're still experimenting at the runtime level. None of this is slow. None of this is stagnant. This is what progress looks like when a technology hits critical mass. Not careful, planned evolution. Chaotic, rapid iteration from every direction at once. Some of it will fail spectacularly. Some of it will become the new baseline. Lowkey, this is the most exciting JavaScript has been in years. Not because of what shipped, but because of what it proves is possible when people stop treating tools as sacred and start treating them as remixable.