Finding Dependable Go Packages
summary
Describes a new site that aggregates concrete signals so choosing a Go package is less guesswork: license, release history, per-version docs, imports and reverse-deps, test status and coverage, and maintainer activity. Cites existing tools like godoc.org, staticcheck and Go Report Card, and recommends module-era rules such as the module import compatibility rule and using proxies like proxy.golang.org or Athens to avoid disappearing dependencies. Shows the site prototype that surfaces these signals for each module version.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:01Finding Dependable Go Packages
- 1:23How do I decide which package to use?
- 4:04Discovery
- 5:05Evaluation
- 5:30License
- 6:26Popularity
- 7:20Code Quality
- 10:25Upkeep
- 13:59If an old package and a new package have the same import path...
- 14:56Indirect Dependencies
- 18:28Maintenance
