The missing guide for deciding between 3rd party library and custom code -JSWORLD 2023
summary
Argues a concrete decision checklist: complexity, speed, API coverage, docs, maintenance, license, illustrated by a tiny jQuery class‑toggle snippet that shows unnecessary branches; recommends measuring popularity beyond stars and says teams use React, GraphQL and TypeScript as examples. Weighs tradeoffs of rolling your own (control versus maintenance cost), warns about decision fatigue and the paradox of choice, suggests deadlines, narrow options and finding a sweet spot, and even verifying behavior by peeking into node_modules.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:21Analysis Paralysis
- 6:49Decision fatigue
- 8:40The Paradox of Choice Selecting speakers for the conference
- 18:32Identify the sweet spot
related talks
24mDrawing the line between 3rd party and custom code
27mDrawing the line between 3rd party and handcrafted code
42mYour library sucks, and why you should use it
49mI'm good at JavaScript, I swear.
40mPIMP Your JS Library or Desgning Non-Shit APIs with JavaScript
23mWhat Can We Learn With JavaScript Fatigue?
01h 02mChoosing a JavaScript Framework
26mInvisible Code: Building JavaScript Libraries For Non-Technical People