Death to JS Libraries
summary
Shows how modern vanilla JavaScript and built-in browser APIs can replace common libraries: using standard DOM APIs instead of jQuery, native data-binding approaches instead of AngularJS, and Web Components without Polymer. Argues you can avoid downloading large library bundles and learn to build applications directly with browser-provided features.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 1:04Death to JS libraries
- 2:51Web evolution disconnect
- 4:59Frameworks vs libraries
- 6:24Unnecessary loops example
- 7:27Date handling: native vs libs
- 8:51Frameworks as tools
- 9:54Native device code
- 11:19Modern APIs replacing libs
- 18:19Mobile APIs and sensors
- 20:27JS library trends
- 21:52Tech selection risks
- 23:36Learn native JS today
- 25:44Tech serving development
- 26:48Closing remarks
- 27:18Q&A
- 31:42Real apps without libs?
- 33:08Trends chart interpretation
- 34:15Commercial pressure vs tech
- 35:41Libraries as standards
- 37:49API support in browsers
- 38:53Code reuse across frameworks
- 40:37JS community fragmentation
related talks
44mModern JavaScript: Moving Beyond jQuery
25mModern JavaScript
40mPIMP Your JS Library or Desgning Non-Shit APIs with JavaScript
21mAsk not what JavaScript can do for you
18mJavaScript Is Dead: 7 Examples Where Modern CSS Is Enough
59mNo Strings Attached: JavaScript without Webpack, Transpilers, or Frameworks
22mThe vanilla way
32mVanilla JS 2019