You should use [insert library/framework], it's the bestestest!
summary
Claims that frameworks win because DOM mutation is the bottleneck get measured against a small gallery stress test that adds 100 images and times JS versus DOM with requestAnimationFrame; results show JS diffing can hit about 1.5 seconds JavaScript time on a Nexus 5 while DOM mutation stays steady. Boot times: vanilla ~50 ms, Polymer ~409 ms, Angular ~518 ms, React (unoptimized) ~1.2 s, Ember ~2 s. A toolchain is built — BigRig with traces, WebPageTest integration and a BigRig runner for scroll/load profiling — and it works to expose real CPU, bandwidth and boot costs.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:07React
- 5:15Guess the Element Count
- 6:58Twitter Responses
- 10:01Ergonomics
- 11:27Pop Quiz 2
- 11:50Costs
- 13:35Libraries vs frameworks
- 17:03BigRig
- 25:47Possible objections
- 27:35Should I use a framework
- 28:15Inversion of control
- 29:51Studying frameworks in detail
- 30:26Data as a decision maker
- 30:52Single framework
- 31:34The web platform
- 32:49Focus on the people
related talks
41mMake JavaScript Faster
14mShould You Favor Performance or Readability?
27mDoing the Least Amount of Work: An Intro to Runtime
28mCSS in JS - beware the Hype!
26mProgressive React
48mThink Fast, First: Empowering a Performance Culture
32mReact Already did that - Developer Ergonomics in 2018
48mBecome a Frontend Developer Ninja using HTML5, JS and CSS3