Your library sucks, and why you should use it
summary
Argues that most JS libraries solve the same small problems and shows concrete shims used: a bind polyfill, trim fallback, and module loaders (requirejs labjs stealjs). Describes porting Dojo widgets to jQuery, running a Dojo server app on Rhino, and proposes common-browser.js with shared feature tests and shims. Counts and concrete tooling matter: avoids hype and promises reproducible fixes, and insists on never more than one library per page.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:15It's Just JavaScript
- 2:07The Good Parts
- 3:38Teh Libraries
- 6:34Libraries are a crutch
- 9:14BASIC AOP 3
- 10:22Philosophically
- 12:01Bind/Curry/Whatever
- 13:59DON'T DO THIS
- 14:53Why not
- 16:49Device Penetration
- 17:30Future Browsers?
- 18:30Commons
- 20:50MDC: Array.prototype
- 24:17Portability
- 26:15MDC: Fn.proto.bind
- 28:18Your library sucks, still
- 30:31Library Benefits
- 32:21Propose: CommonBrowserJS
- 38:41Small Problems are Easy
- 40:27First pass has.js
related talks
40mPIMP Your JS Library or Desgning Non-Shit APIs with JavaScript
24mThe missing guide for deciding between 3rd party library and custom code -JSWORLD 2023
26mInvisible Code: Building JavaScript Libraries For Non-Technical People
21mAsk not what JavaScript can do for you
06mLightning talk from Andrey Sitnik
05mEffective Dependency Management in JavaScript
24mDrawing the line between 3rd party and custom code
50mIs your JavaScript ready for the Enterprise