Interleaved Deltas
The article discusses the concept of weaves, a data structure used for version control systems. It highlights the simplicity and sophistication of Git while contrasting it with the more complex interleaved deltas used in earlier systems like SCCS. The author shares insights on the algorithms behind weaves and their role in managing file revisions.
- ▪Weaves are sequences of instructions for reconstructing file revisions.
- ▪The Source Code Control System (SCCS) utilized interleaved deltas to manage revisions one file at a time.
- ▪Weave blocks can overlap, allowing for complex relationships between different versions.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Mmapped |
| Canonical URL | https://mmapped.blog/posts/51-interleaved-deltas |
| Publication time | Tue, 26 May 2026 14:30:21 +0000 |
| Retrieval time | 2026-05-26T14:37:49.954Z |
| Last seen | 2026-05-26T14:37:49.954Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | None |
| Cluster logic | Not yet clustered, or no peer story found in the clustering window. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Interleaved deltas✑2026-05-22dsa Weave structureActive revision setReconstructing revisionsComputing deltasExtending weavesReconstructing deltasConclusionExercises A weave has a reputation of one of the most reinvented data structures in history.Victor Grishchenko, Mikhail Patrakeev, Chronofold: a data structure for versioned text Progress is often viewed as a transition from simple to complex. Although individual systems do become more complex over time, long-term progress happens when new ideas and advances in hardware make simple designs feasible. Think of the simplest version control system you can imagine. It probably stores project snapshots in a backup directory. Maybe it compresses files for efficiency. Add hashing for content addressing, and the sketch starts to resemble Git.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Mmapped.
Discussion
0 commentsMore from Mmapped
