The Good, The Bad, The Web Components
summary
Web Components are already on ~20% of Chrome page loads and shine for small, dependency‑free widgets: a server‑rendered counter increments with a click using the Custom Elements API, but Shadow DOM introduces layout shift unless scripts run early. Declarative Shadow DOM fixes that but lacks Firefox support without a polyfill. Platform gaps push SSR to tools; WebC and Enhance compile reusable shadow templates to HTML so pages ship zero client JS by default and preserve progressive enhancement.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:25State of web components
- 5:17Level 1: Custom elements
- 12:23Level 2: Shadow DOM
- 17:27Level 3: Declarative Shadow DOM
- 20:51Level 4: Server-side rendering
- 26:16Web performance philosophy
- 27:08Q&A and closing
related talks
24mThe Good, The Bad, and The Web Components
28mThe (Real) State of Web Components
32mFuture CSS in Web Components
29mBreak out from the framework: Web Components to the rescue
42mWeb components and the future of web development
24mWeb Components: It's all rainbows and unicorns! Is it?
36mWeb components - A whirlwind tour thru the future of the web
36mThe State of Web Components