Tough Decisions: the complexities of maintaining a popular open source project
summary
Angular is used by millions and the repo hovers around ~1,000 open issues and ~100 PRs while React, Vue and Svelte show similar backlogs; long‑running issues persist because of finite resources, prioritization, lost institutional knowledge, and a Google monorepo policy of “you break it you fix it.” Breaking changes land only in a twice‑yearly breaking change window and sometimes require manual work because a minimal repro shows migrations are impossible or too costly. Submit focused PRs with tests and docs.
AI-written summary · about
chapters (12)
- 0:00Tough decisions in open source
- 1:10Open source maintainer life
- 2:33Issue triage scale
- 6:26Long-standing issues persist
- 9:55Prioritization constraints
- 12:21Use case complexity impact
- 14:08Breaking changes challenges
- 19:24Legacy code support
- 20:48Google monorepo & Angular constraints
- 23:18Open source maintenance realities
- 26:53Reporting issues effectively
- 28:00Q&A
