Why we need UI libraries/frameworks by Khachatur Virabyan (Arm) | JSConfAM19
summary
Argues that a UI library is not ideology but a tool: gives a concrete claim about maintenance and performance, measures real benchmarks: 40% faster render and 30% less memory against plain DOM code, compares uses React and vanilla JS implementation and shows the tooling chain (bundler, profiler, devtools). Builds a small single‑page demo (avatar feed + routing) and proves it deploys and behaves under load — the demo works and the measured savings are reproducible.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:02Single-page apps rise
- 6:14UI dev challenges
- 9:48Component architecture
- 13:01Performance optimization
- 16:55Mental models
- 20:10Avatar components
- 23:00The necessity of UI frameworks
- 26:06WebAssembly and UI
- 28:12Conclusion
related talks
32mUI Development Made Simple
25mBuilding Loveable UIs
44mThe UI Component Library You Always Dreamed Of
44mBest Practices on building a UI component library for your company
35mBuilding reusable UI libraries with React
14mReusable UI Components in a Framework Multiverse
01h 04mBuilding Design Systems for Scale: From Tokens and Components to Motion & AI Tools
35mDesign system - From a Developer Point-of-View