Conceptual, architectural explainers — how a subsystem actually works underneath.
A live query doesn't just return files matching a condition once — it keeps the result set current automatically, as files are created, changed, or deleted, for as long as the query stays open.
Haiku's Media Kit models audio and video processing as a graph of connected nodes passing buffers to each other in real time — the same conceptual model professional media software still uses today.
What actually happens on disk when you brew install something, and why Homebrew's design differs from a traditional Linux package manager.
A walk through what actually happens between powering on a Haiku machine and reaching a usable desktop, and where things most commonly go wrong along the way.
A stage-by-stage tour from power-on firmware through GRUB, the kernel, initramfs, and systemd reaching a running system.
Installing a package on Haiku doesn't copy files onto disk at all — it mounts the package itself as part of a virtual file system, which is exactly what makes activation and rollback instant.
How pf's rule evaluation model, tables, and anchors fit together on FreeBSD, with a ruleset you can adapt for a real host.
Haiku's native C++ API isn't one monolithic library — it's a set of separately-scoped 'Kits,' each owning one concern, that together define what writing software for Haiku actually looks like.
Haiku applications don't poll for events in a manual loop — they define Handlers, and let a Looper thread dispatch messages to the right one automatically.
How macOS verifies that an application hasn't been tampered with and hasn't been flagged as malware, before it's ever allowed to launch.