Package managers keep using Git as a database, it never works out

kept by eddie dec 29, 25

Using Git as a package manager backend causes performance and scaling problems as ecosystems grow, leading to workarounds like proxies and sparse checkouts.

Package managers keep using git as a database, it never works out
Package managers that use git as a database for registry data inevitably hit scaling limits, forcing migrations to HTTP-based or CDN-backed solutions.
also on #scaling, Nix, #package-management, Homebrew, #git, #software-engineering, #developer-tools
Towards self-driving codebases
Cursor built a multi-agent harness that recursively delegates coding tasks across planners and workers, achieving ~1000 commits per hour on a browser research project with minimal human intervention.
also on Cargo, #git, GitHub, #software-engineering, #developer-tools
GitHub's plan for Agents — Kyle Daigle, GitHub
GitHub COO Kyle Daigle discusses how AI agents caused platform activity to surge 1400% in 2026, straining infrastructure and forcing GitHub to rethink open-source social contracts and reliability.
also on #scaling, GitHub, #software-engineering, #developer-tools
Your executable is a SQLite database
Replacing ELF with SQLite as an executable format (SELF) yields queryable binaries with ~1% size overhead, enabling closure‑based dependency packing and SQL‑based tooling.
also on Nix, #open-source, #software-engineering, #developer-tools
Your CI should be disposable
The article argues CI should only schedule builds, delegating actual builds to local tools like Docker or Nix so workflows remain runnable even if CI services fail.
also on Nix, #software-engineering, #developer-tools