Make it Boring

on YouTube ↗34m

" summary

Argues for choosing progressive enhancement and server-rendered routes with hydration over default SPA patterns, with concrete tradeoffs: slower-first-load but far better accessibility and resilience. Cites infrastructure data — 58% of low-income Cleveland households lack broadband and one-third of Americans lack >dial-up home internet — and a failed experiment example, Hot Sauce 3D sitemap didn’t win users. Recommends HTML, CSS, platform APIs, flexbox and grid, and measured use of client-side routers.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 0:34Presentation Overview
3. 1:19The subprime mortgage crisis
4. 7:59Making web development exciting
5. 15:30What are you trying to serve
6. 18:48The web is frustrating
7. 23:10The web is boring

" related talks

• 40mMake it BoringJeremy Wagner · NDC Oslo 2020
• 34mWeb development isn't about you, dudeCharlie Owen · CSSConf Budapest 2017
• 32mMake Websites, Not AppsSoledad Penadés · CSSConf.Asia 2016
• 41mThe power of progressive enhancementAndy Bell · Inclusive Design 24 (#id24) 2018
• 34mWe need to talk about the front webAngela Ricci · ffconf 2023
• 30mDoes Progressive Enhancement Have a Place in Today's Web?George Brocklehurst · WindyCityRails 2016
• 22mProgressive EnhancementJames Halliday · NodeConf.eu 2013
• 51mProgressive EnhancementLee Byron, James Kyle, Jack Franklin, Jeremy Keith, Lyza Danger Gardner, Remy Sharp · Edge Conference 2015