Panel - Package Managers: Before and After npm
summary
Panel records concrete outcomes: bundler solved app-level conflicts (the rack version clash) so apps can pin exact working sets; cargo enforces repeatable builds and crates.io enforces a no-deletes policy plus a flat namespace, provoking name-squatting tradeoffs; CocoaPods moves specs out of a giant git repo into an authenticated API after a mass-deletion incident broke builds; proposed server-side checks include automatic semver/type-change validation to reject accidental breaking releases.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:58Meet the panelists
- 3:22Defining the problem
- 9:27Dependency Resolution
- 10:29Dependency Hell
- 14:56Ruby
- 19:39Cocoapod
- 23:31Dream Feature
- 25:32Biggest Challenge
related talks
33mPanel: Composable Platforms in the Real World: What Works, and What Really Doesn't
28mArgo CD Maintainer's Panel
01h 11mThe State of Package Management in C++
08mAll About Dependencies
10mStay calm and stress-free by using a package manager: an overview of vcpkg
05mProject Lightning Talk: Container Builds at Scale with Buildpacks
30mBringing Continuous Delivery to Open Source
42mUsing vcpkg in anger