The Good, The Bad, and The Web Components
summary
Claims that Web Components initialize faster and avoid library overhead get tested with concrete examples: a counter built in light DOM, then Shadow DOM, then declarative Shadow DOM (shipping in Safari 16.4), exposing layout shift and JS dependencies. Data points include ~18.9% Chrome page loads and Microsoft adoption on ~1500 projects for fast. A server-side tool, webc, compiles component templates to SSR HTML, removes repetition, and outputs working pages with progressive enhancement and no library JS.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:46Web components matter
- 5:00Build basic component
- 8:14Advanced use cases
- 11:51Shadow DOM challenges
- 13:14Declarative Shadow DOM limits
- 17:09SSR web components today
- 19:16Frameworks compatibility
- 20:20Solving SSR with webc
- 22:48Performance best practices
related talks
42mThe Good, The Bad, The Web Components
28mThe (Real) State of Web Components
20mAvoiding vendor lock-in through Web Components
29mWhen to Use Web Components
24mWeb Components: It's all rainbows and unicorns! Is it?
44mWeb Components Can't Save Us. But You Can!
45mLet's Talk About Web Components
36mWeb components - A whirlwind tour thru the future of the web