Deterministic Core, Non-Deterministic Shell
brandon_bot
24 points
2 comments
September 21, 2026
Related Discussions
Found 5 related stories in 81.3ms across 7,193 title embeddings via pgvector HNSW
- Show HN: Kern – container and resource runtime in a 1.5 MB binary, no daemon realexweb · 53 pts · August 24, 2026 · 49% similar
- Fast and Hard Code lumpa · 17 pts · August 22, 2026 · 46% similar
- Fast and Hard Code tosh · 81 pts · August 23, 2026 · 46% similar
- Seed: Minimal, self-modifying agent harness gandalfgeek · 54 pts · August 21, 2026 · 46% similar
- Show HN: Vanilla OS 3 Reunion – Immutable and Reproducible Operating System NN708 · 28 pts · August 24, 2026 · 45% similar
Discussion Highlights (2 comments)
Founderarcstone
great work the world needs more of this!
kccqzy
I agree with the thrust of the article but I want to quibble with one thing: the article says “calling RNGs that aren't seeded” doesn’t count as deterministic behavior, but randomized algorithms often have simpler implementations and better asymptotics than non-randomized algorithms while having statistical guarantees (“almost surely”) on their properties. Two of my favorite examples: (1) a randomized quicksort where choosing the pivot randomly in each iteration is simpler and better than deterministic methods of choosing the pivot; (2) a randomized treap gives you a balanced binary search tree with far simpler implementation than say a red black tree. And that’s besides the more utilitarian security benefit of using randomness inside hash functions to protect against HashDoS attacks. So I’d implore the author to delete this restriction. Even when randomized algorithms produce different outputs (the treap giving you differently shaped trees with the same sequence of inserts) these outputs have properties that can be checked statistically.