Frameworkless Frontend Development
summary
A prototype production app manages 20 players and 4 teams without any front-end frameworks, using plain ECMAScript, W3C browser APIs, Babel for transpiling and Jest for tests, and no runtime package dependencies. It uses an observable state pattern where setters emit immutable copies, a render function that replaces document.body on each state change via requestAnimationFrame (no virtual DOM), and the codebase is tested and deployable; potential performance limits are acknowledged and could be addressed later by adding a virtual DOM.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:09Why use frameworks
- 6:53Demo without frameworks
- 18:35Team reactions
- 21:05When to avoid frameworks
- 27:33Technical choices
- 33:45Conclusion
related talks
45mNo framework frontends in practice - use the platform!
41mLow-budget JavaScript: composable frontends that are fun and friendly
44mApplications instead of libraries: Micro frontends implemented through module federation
38mBreak Up With Your Frontend Monolith
30mMicro Frontends in React — a State of the Art Approach
36mMicro Frontends in Action!
45mMicro Frontends in Action!
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
