Does The Browser Have A Future
summary
Argues the browser risks being squeezed by native mobile apps while core web tech (HTTP, URLs, HTML) stays healthy; demonstrates server-side strengths with actual examples: a parallel identity-checker built in Go parallel channels and Erlang powering WhatsApp; cites scale like 75,000 Cassandra nodes with tens of petabytes; shows how many mobile top games use C++ engines for true cross‑platform reuse and why PhoneGap/Cordova fails for polish; diagnoses broken DOM, JS and CSS stacks and points to fixes like Zen Grids cutting CSS size fivefold.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:14Browser declared dead
- 3:40Server-side golden age
- 8:55Client-side challenges
- 11:45Functional programming tools
- 15:36Native vs web apps
- 19:25Management pressure
- 21:53SDKs vs browser limits
- 23:18Browser API crisis
- 27:30CSS grid problem
- 31:41JS framework explosion
- 33:28Risk of wrong tool
- 34:52Fix or replace browsers
- 35:55Vendorless web future
