Most syncing contexts have to assume that one peer might be gone for an arbitrarily long time and need to re-merge later.

2024-05-13 · Bits and Bobs 5/13/24

You save a ton of complexity if you can assume any of:

Roughly 24/7 availability of peers, with only minor interruptions.

No need to automatically merge peers cleanly in the future

If you can simplify that, you cut out a 20% edge case that causes 80% of the work.

More on this topic

From other episodes

Collaborative text editing with offline sync is hard.2026-03-23
Designed versus spontaneous order 2026-03-02
Your personal use case is likely an edge case for the aggregator.2025-10-27
One reason computer systems get more complex: handling the exponential blow up of all edge cases for all users.2025-10-27
WYSIWYG systems almost always have some weird edge cases that are hard for users to reason about.2025-03-10
It is not possible to fully enumerate in human language all of the edge cases of a real world phenomena.2025-02-24
LLMs are unlike normal programs in that they allow open-ended output.2025-01-06
Someone who embraces complexity realizes the tensions are fundamental and cannot be resolved, only dynamically and contextually balanced.2024-11-04