Platform · 2009–now · Platform Wars

Node.js

JS on the server. Unified the stack and created a package ecosystem that is both miracle and hazard.

Node stuck by making I/O-bound APIs fast to write for front-end refugees who already knew JS. Single-threaded quirks hurt; ecosystem velocity healed. It is not the best server runtime — it is the default one for web teams.

javascript server async

Case studies

Parse shutdown — migrate or die — Forced migrations under a hard EOL clock; months of unpaid rewrite for many teams

Context

Frameworks fought for the runtime

Front-end frameworks consolidated power; TypeScript became table stakes; Next and friends absorbed routing, data, and deploy gravity. Serverless and Jamstack rebranded old ideas with better CDNs, then cooled when auth and personalization refused to stay static. Blockchain-for-CRUD and big-bang rewrites collected dumb budgets. The winners were boring platforms with ecosystems — React gravity, Rust where systems care, Vite for greenfield bundling. The losers were narratives that skipped product-market fit or treated every App Router rewrite as destiny.