Platform Wars

JS with a typechecker that conquered the ecosystem. The rare fad that became the floor.

The only language that runs in every browser. Accidental monopoly turned deliberate platform.

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

Memory safety without GC pauses. Climbing from systems niches into cloud infra and WASM.

React with routing, SSR, and deployment opinions — App Router gravity and vendor lock-in as the default web stack.

Utility classes in markup upset purists and accelerated shipping. Design systems without meeting paralysis.

Python APIs with types and OpenAPI for free. The default backend for ML demos that became the default for a lot else.

Angular-style structure for Node backends. Enterprise comfort food with decorators and modules.

ESM-native dev server that made webpack feel instantaneously obsolete for new projects.

Functions as the unit of deploy. Brilliant for spikes and glue; awkward as a whole product architecture.

Pre-render + CDN + APIs. The brand cooled; the pattern (static where possible) stuck.

HTML as the engine of application state — a deliberate counter to SPA maximalism. Peak backlash; now a plateau, not a climb.

Batteries-included SPA platform for teams that want opinions and CLI scaffolding.

Chromium in a trench coat. Slack, VS Code, and RAM usage everywhere you look.

Paint your own pixels on iOS and Android from one codebase. Google's bet against native UI fragmentation.

React components on native views. Share logic with web until platform differences ruin your sprint.

Auth, realtime DB, and hosting as a product. Prototype paradise; vendor lock purgatory at scale.

Portable bytecode beyond the browser. Slow burn with real teeth in edge and plugin runtimes.

All-in-one JS runtime that actually feels fast. Winning scripts and side projects while production waits for edge cases.

Web standards–first React framework with nested routes and forms. Merged into React Router; the ideas survived the brand.

Google's language that found purpose as Flutter's syntax. Rare case where the UI framework rescued the language.

Clients ask for exactly what they need — and sometimes invent a second backend team to make that safe.

Drag-and-drop apps for the enterprise backlog. Useful for internal tools; fantasy as a full replacement for engineering — a pitch later absorbed by AI demos.

C without the footguns — in theory. A systems language beloved in blog posts and absent from most job boards.

Node reimagined with TypeScript native and permissions. Correct instincts; wrong moment against npm gravity.

Fine-grained reactivity without a virtual DOM. The framework perf nerds cite when explaining why React rerenders hurt.

Resumability and zero-JS-first marketing. Correct diagnosis of hydration pain; crowded prescription aisle.

Decentralize data ownership like microservices for warehouses. Real org problem; often a logo refresh for the same broken pipelines.

$ Consultancies sold domain ownership and federated governance while teams still could not agree on a customer ID. Slideware outpaced catalog tooling by years.

Replace the working system instead of strangling it. A perennial money pit with new branding each decade.

$ "We'll freeze features and rewrite in the hot language." Multi-year projects shipped late, incomplete, or not at all — while competitors iterated on the ugly system that made money.

Erlang semantics with friendly syntax on the BEAM. The language your functional meetup loves and your employer has never heard of.

Distributed consensus for problems that needed a database and an audit log.

$ Enterprises funded "innovation labs" to put loyalty points and supply-chain spreadsheets on ledgers. Most pilots ended as slide decks; the gas fees and audits did not.

Wallet popups as UX. A subculture with real tech under a mountain of token incentives.