Breaking changes

on YouTube ↗46m

" summary

Shows concrete breakages: replacing a numeric status code with a string breaks callers using === and turns arithmetic into string concatenation, the array flatten debate exposes ambiguous semantics, and Node’s Buffer ambiguity gets fixed by splitting into Buffer.from and Buffer.alloc. Semantic Versioning is coarse — zlib 1.2.9 (Dec 2016) rejects previously tolerated compression values and causes crashing servers, taking ~10 months to mitigate. Practical fixes: prefer Maps/Sets, use named-argument objects, assert input types, publish runnable examples and tests.

AI-written summary · about

" chapters (11)

1. 0:00Breaking changes James Coglan
2. 1:42THE SOFTWARE IS PROVIDED AS IS
3. 7:26Changing interfaces
4. 15:18Conceptual complexity
5. 20:59Implied contracts
6. 23:47Side effects
7. 32:29Never break anything
8. 35:52Communicate
9. 37:33Avoid brittle constructions
10. 41:43Documentation
11. 42:45Automated testing

" related talks

• 41mBreaking ChangesJames Coglan · Øredev 2019
• 39mWe fail to follow SemVer and why it needn't matterStephan Bönnemann · JSConf Budapest 2015
• 44mBackwards Incompatible TalesMarco Pivetta · phpDay 2019
• 46mThe Unexpected Demise of Open Source LibrariesLiran Tal · Critical Software Summit @ Open Source Summit Europe 2022
• 37mNode.js Package Maintenance...Bethany Griggs, Glenn Hinks, Darcy Clark, Dominykas Blyze, Rodion Abdurakhimov · OpenJS World 2021
• 35mThe Social Coding ContractJustin Searls · MountainWest JavaScript 2015
• 26mHow to Break an API: How Community Values Influence PracticesChristian Kästner · JSConf EU 2017
• 01h 07mRuby Committers and the WorldRubyKaigi 2026