From Frameworks to Superframeworks
summary
Discusses how using popular JavaScript frameworks can lock application code into non-reusable patterns, force unnecessary refactoring and copy‑paste, and how early architectural choices affect future frontend development. Presents reactive-di, a solution combining dependency injection and reactive programming ideas (influenced by mobx, mol, cellx, Angular2 DI) that acts like a lightweight ‘container’ for app state and composition to reduce framework lock‑in.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 1:16Superframework idea
- 4:31Pure functions and context
- 6:16React components limits
- 9:54Pure component reuse issues
- 11:38Context in pure components
- 13:47Stateful components limits
- 15:32State and Redux
- 16:57React Context limits
- 18:23Dependency Injection in AngularJS
- 21:14TypeScript/Flow DI issues
- 22:37Framework monolith problems
- 25:47Routing and layer mixing
- 27:39Framework migration issues
- 29:45Optimization and architecture
- 33:20Reactive streams benefits
- 35:50Reactive library implementation
- 39:45Unobtrusive streams and DI
- 41:49Code volume and complexity
- 43:15Frontend alternatives
- 46:07Q&A
related talks
32mWhy Invent a Framework and How to Live with It?
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
28mMicro-Frontends anti-patterns
32mMiss the forest for the trees: How frontend developers fail to be engineers
51mReactive Programming with JavaScript
20mSacrificial Architecture in modern web development
30mThe age of hooks Framework agnostic frontends might be surprisingly powerful
48mDive into frontend frameworks to understand their reactivity🔬⚛️