Skip to content

Still Brook.

Observations & other curiosities

Notes on software
and the things
we make.

Open the notebook
An engraved computer on spindly legs beside a brook, with a bird, a leafy twig, and a curling paper tape.
Fig. 01 — A machine for wandering thoughts.

Latest essay

One open file, a tray of half-made thumbnails, and two names for the same pixels. Three things programming languages can now help us keep straight.

Read the essay
Three photographs of a diving kingfisher hang above a developing tray.
Illustration generated with GPT Image

Pages from the notebook

106 of 132 essays

106 essays found. Page 4 of 9.

  1. The hinges are the product

    comp0 treats accessible interaction, native form contracts, and server rendering as the durable product, leaving every visual decision to the application.

  2. Please, sir. I’m tired.

    Codex usage limits have been reset for outages, launches, milestones, cache bugs, vibes, and literal RESET week until the exception became a public ritual.

  3. The garage, years later

    Revisiting Reddit's one-person languages by age instead of debut shows what solo years actually produce: a plan to freeze, a dormant design other people keep alive, an eight-year 0.3, a line-count budget that holds, and a release routine older than Linux.

  4. The document needs a sandbox

    PDF preserves the page by making every reader parse a programmable container, infer missing semantics, and defend itself against malformed or active content.

  5. Infinity on demand

    Haskell’s infinite lists are finite producers whose usefulness depends on productivity, short-circuiting consumers, fair enumeration, and forgetting prefixes the program has already used.

  6. The thunk should be the fallback

    Default laziness becomes plausible when compilers evaluate demanded work eagerly, represent common delays as inspectable data, and reserve closure thunks for the cases they cannot understand.

  7. Bytes stop pretending to be text

    ECMAScript's Base64 methods put binary conversion on Uint8Array and make callers choose how forgiving a decoder should be.

  8. The compiler needs a test stand

    Five familiar programs go into a benchmark filter and four come out labeled with how they would ruin the measurement; cmark survives, pinned to a contract.

  9. A value can carry proof

    Pattern matching on a GADT key teaches the type checker the result type, turning an unchecked registry cast into an ordinary lookup.

  10. Evidence belongs in the result

    Three programming-languages papers ask what inspectable evidence must accompany a bug report, a parallel-cost bound, or a generated test.

  11. The call was cheaper

    A controlled inline benchmark shows how disassembly and code size can explain a performance result that call-count intuition gets wrong.

  12. The edge case has a derivation

    Reducing JavaScript’s [] == ![] produces a deterministic chain of coercion rules and identifies where code should reject the default conversion.

A note in the margin

A little curiosity goes a long way.

Still Brook is an independent journal about software, systems, and the quiet decisions that shape what we make.