Tag

Notes tagged “content-addressing”

Every note filed under content-addressing, newest first.

A filtered view of the notes.

2026

  1. The URL Is the Hash

    Content-addressing on the wire — how the web quietly became a content-addressed store, where fingerprinted URLs and Subresource Integrity are real Merkle edges and the cache that looks most like one isn't.

  2. You Don't Want Separate Repos

    A repository is a database; splitting a subproject out trades a content hash for a version string — and there's only one case where that trade is actually forced.

  3. node_modules Is the Heaviest Object in the Universe

    The same "the hash is the identity" idea that powers a build cache also explains why pnpm stores on disk what npm copies a hundred times over.

  4. The Hash Is the Identity

    Content-addressing in the build cache — content-addressed storage and Merkle trees turn a build cache into a shared resource, so your build is proportional to anyone's change.

  5. A Little Uncertainty Buys a Lot of Space

    Bloom filters trade a small chance of being wrong for an enormous saving in memory — a bargain storage engines take and build systems, so far, refuse.

Type to search · ↑↓ to move · ↵ to open · Esc to close