4d ago · 16 min read · RAM is scarce. Processes are greedy. And yet, somehow, your laptop runs dozens of programs simultaneously without them trampling each other's data. The secret weapon is paging — a beautifully elegant
Join discussion
May 26 · 14 min read · The Illusion Every Program Lives In Open your task manager. Notice that Chrome thinks it owns 4 GB of memory. Spotify thinks it owns 2 GB. Your IDE thinks it owns 8 GB. Add them up and you'll often ex
Join discussion
May 20 · 11 min read · When I started building HozonDB — a relational database engine from scratch in Rust — I made a deliberate choice to keep the storage model simple. Pages, rows packed one after another, a pointer to th
Join discussion
May 15 · 4 min read · Every program you run believes a quiet, comfortable lie. It thinks it has a vast, clean stretch of memory all to itself — starting neatly from address zero and stretching out as far as it needs. The s
Join discussion
May 12 · 10 min read · Concurrency is one of those topics that feels deceptively simple until it bites you at 3 AM. You've got multiple threads, they share some data, and suddenly your application freezes, produces garbage
Join discussion
May 10 · 11 min read · I Built a Message Broker in Go From Scratch — Here's What I Learned TL;DR: I built streamq — a message broker in Go with WebSocket/SSE delivery, WAL-backed storage, Prometheus metrics, and an embedde
Join discussion
May 10 · 6 min read · Every program eventually has to wait — for a timer, a lock, a network packet. The question is: what should the CPU do during that wait? The answer has a surprisingly large impact on performance, power
Join discussion
