The Frankenstein Framework - The Polyglot future of the web
summary
Claim: ES6 modules let different frameworks be composed instead of chosen. Demo uses ES6 modules with webpack + Babel, wires Angular 2 dependency injection to instantiate models, renders a React component, and routes with director/Flatiron while using a fetch polyfill to load GitHub data. The Frankenstein app builds and runs via webpack dev server so the composition works end to end, but the approach lacks docs and community support so scalability for large teams remains questionable.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:22Document Web Era
- 3:07The Hybrid Web
- 4:03The Application Web
- 4:41Frankenstein's Frustrations
- 6:01Code Sharing
- 6:19The Platform Has Changed
- 6:55The Ecosystem Has Changed
- 8:28Webpack
related talks
45mNo framework frontends in practice - use the platform!
36mMicro Frontends in Action!
44mJavaScript in 2017: You might (not) need a framework
25mAdvanced Micro Frontends: Multi-Version and Multi-Framework Scenarios
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
41mThe future is modules not frameworks. JS modules Architecture demo.
43mDiversity in the World of Web Components
40mAngular, React, Vue and Co. – peacefully united thanks to Web Components and Micro Apps