We need to talk about the front web
summary
Argues the front web loses its strengths—open standards, semantics and separation of content style and behaviour—to heavy JavaScript, utility class soup and proliferating frameworks like Angular and React, producing pages that take 10+ seconds to feel usable and projects stuck months on dependency updates. Recommends concrete fixes: teach HTML/CSS/semantics properly, stop outsourcing front to ill‑trained fullstack shortcuts, pair developers with designers and content strategists, and prefer resilient, standards‑based implementations instead of client‑side everything.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:08Web strengths and standards
- 4:05Content style and behavior
- 6:17Power of semantics
- 7:19Tag soup and style attributes
- 9:46Standards rebirth in 2004
- 10:28Divs spans and classes soup
- 12:19HTML foundation
- 14:50Performance decay
- 16:37Broken abstractions
- 18:04Root causes of problems
- 21:00Developers despise HTML/CSS
- 23:08CSS and front challenges
- 24:59Cool kid syndrome
- 26:03Fullstack myth flaws
- 28:14Fixing front web training
- 30:40Ending Fullstack myth
- 31:45Working with designers
- 33:12Cherishing the web
related talks
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
43mAre We Building the Web the Right Way?
38mThe Front-End Future
51mThe Business Of Front-End Development
40mScaling Frontend Development
50mComposable decoupled frontends: the Jamstack and beyond
58mAlways crashing in the same car (the state of front end web development in 2022)
29mQuo vadis, frontend?