The Winding Road Towards JS Interoperability
summary
Argues that real interoperability comes from aligning with standards not frameworks, citing ES Modules, web components, and TypeScript interfaces as practical fixes; shows tools and efforts like Dojo exporting components as web components, Ionic’s Stencil compiler, Svelte’s minimal runtime, and Project Evergreen docs. Notes concrete gaps: dynamic import and package mapping land in Chrome and Safari while Edge/Firefox catch up, hundreds of conflicting promise libs historically, and a 250‑page framework review that found frameworks interoperated less than they could.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:23Trends
- 4:48Patterns & standards
- 5:58TypeScript
- 7:31Reactivity
- 9:34Interoperability
- 10:35Classes
- 11:50Interfaces Rendering Routing
related talks
17mJS In The Enterprise - Lessons Learnt
43mWeb Components: From 'Why Not?' to 'Why Now!'
39mReinventing the Wheel for Every New JS Framework, Is It Worth It?
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
56mComponents and Modules
52mWeb Components Can Do That?
28mWhere the future is heading for JS Frameworks…
36mThe Road to Native Web Components