The Future is Frameworks, not Modules
summary
Claim: frameworks beat opaque modules by making context first class and restoring composability. Implementation: a framework called fluid infusion uses a JSON configuration and an inversion‑of‑control demands block so functions are resolved by matching context names in a global resolvable tree. It supplies eventing renderer data binding and accessibility helpers and demonstrates that contextual rules plus the JSON model let applications adapt presentation and behavior without duplicating pages rather than relying on opaque module vaults.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:10The problem of software
- 6:34JavaScript is a GREAT environment
- 7:16What is in Fluid Infusion?
- 8:26Elements of the solution
- 9:50A "demands block"
- 15:33Designing for Context
related talks
06mFramework Inception with Micro Frontend Composition
32mWhy Invent a Framework and How to Live with It?
51mBeyond the Framework: Building for the Next Decade of the Web
49mFrom Frameworks to Superframeworks
22mTowards a frameworkless world
18mA framework author's case against frameworks
12mLiberating your Application from Framework Tyranny
38mWhat's The Framework of the Future?