Quiver.JS - Rethinking Web Frameworks
summary
Quiver claims a concrete rework of web frameworks: it implements a middleware-first component system on Node using ES6, shipping CSP-style streams and promise APIs, distinct stream and HTTP handlers that return streamables, and configurable dependency-injection filters (builders + filters) so middleware can construct and inject resources. The repo shows a working foundation: component graphs run as servers or internal function calls for unit tests, and core pieces are implemented with plans to add templating and auth.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:20About Me
- 0:53Too Many Frameworks
- 1:15Why Use Frameworks
- 2:22Model, View, Controller
- 3:48Scaling Frameworks
- 10:44Node Handler Is Hard
- 12:19Middleware Is Hard
- 14:16The Quiver Solution
- 15:36Stream Channel
- 17:09Transform Stream
- 20:55Stream Handler
- 28:28Component Loading
- 29:09Composition
- 29:59Component Graph
related talks
20mQwik
21mFROM ANGULAR TO QWIK: THE FRAMEWORK THAT CHANGES THE PARADIGM
18mA Brief History of Web Applications — Why the Qwik JS Framework Is Innovative
21mFROM ANGULAR TO QWIK: THE FRAMEWORK THAT CHANGES THE PARADIGM
49mJavaScript Streaming - A Qwik glimpse into the future
45mJavaScript Streaming - A Qwik glimpse into the future
29mQuo vadis, frontend?
32mWhat's Happening in the JavaScript Ecosystem?
