Web Components: From 'Why Not?' to 'Why Now!'
summary
Argues that 2018 is the tipping point: web components are usable now because browsers and frameworks are catching up. Lists the four platform APIs—custom elements, shadow DOM, HTML templates and (legacy) HTML imports—and shows concrete moves: Polymer 3 shifts to ES6 modules and npm, Polymer CLI and starter kits scaffold shop/news demo apps, and a “purple” loading pattern + a purple server for performance. Notes interoperabiity tests, Redux support for state, and that IE still needs polyfills.
AI-written summary · about
chapters (14)
- 0:00Start
- 1:34About Me
- 12:00That are web components?
- 12:43What are these platform APIs?
- 17:59How do I define a custom element?
- 18:54How do I use a custon element?
- 23:11Track Interoperability/Issues
- 27:26Polymer 3.0 released / May 2018
- 28:05The Polymer Project from Google
- 29:40Feature/Code Walkthrough
- 34:12Create/App Toolbox & CLI
- 34:46polymer-3-starter-kit
- 35:00Build & Deploy / Issues & Options
- 37:272018/PWA Starter Kit
related talks
21mThe Year of Web Components
41mWeb Components en 2019, on en est où ?
36mWeb components - A whirlwind tour thru the future of the web
59m2018 - The Year of Web Components
30m2018 - The Year of Web Components
24mWeb Components: It's all rainbows and unicorns! Is it?
49m2018 - The Year of Web Components
46mWhat ever happened with Web Components?
