Moving JS from Libraries to Polyfills

on YouTube ↗20m

" summary

React moves toward a minimal API surface and prefers language features over special libraries while rolling experimental code behind polyfills first then replacing libs when standards stabilize. Practical problems include global Prototype collisions that broke mols and string contains versus includes, versioning and CDN single points, and early native implementations being slow so teams override native implementation until engines optimize. The working workflow is transpile modern syntax down and use polyfills as a service.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 3:07Facebook
3. 5:10Adoption Curve
4. 7:18Problems
5. 7:59Versions
6. 8:40Break the spec
7. 11:19Break the prototype
8. 13:15New syntax
9. 15:14Too many options

" related talks

• 27mUnderstanding JavaScript Libraries via React and the React EcosystemAndrew Pinkham · DjangoCon US 2017
• 45mRefactoring the polyfills recipeDmitriy Kholstinin · HolyJS 2025 Autumn
• 59mThe effect of React on web standardsKarl Horky · React Alicante 2017
• 24mMinimal API Surface AreaSebastian Markbage · JSConf EU 2014
• 44mJavaScript in 2017: You might (not) need a frameworkDavid Vujic · NDC Oslo 2017
• 54mJavaScript Essentials for Programming with ReactVenkat Subramaniam · Developer Summit 2020
• 11m99 Ways to Take Away Your Ugly PolyfillsArtem Yavorsky · JavaScript fwdays'18
• 42mIntegrating React Into Legacy ProjectsMartin Chaov · <React.NotAConf /> 2018