In July, Ukrainian developer Valentyn Danylchuk (itch.io handle mini000) released something called beeper — what he calls "a toy subtractive synth." Sixteen controls, no more. You steer it with arrow keys, toggle sustain and solo with the space bar. Twelve preset timbres, mapped to the keys 1 through 9, 0, minus, and equals, cross with a handful of built-in demo loops to give a hundred and forty-four starting points, and after that you're on your own. The whole thing is about eighteen hundred lines of C, written first for ESP32 embedded hardware, then recompiled to WebAssembly so it plays in a browser. It sat quietly for two months until Hackaday wrote it up in September, showing it running on a Tanmatsu handheld built around the ESP32-P4.

Danylchuk states his own constraint plainly: "No MIDI, no saving, no chord level polyphony: it is just a music toy with some potential for learning." That sentence is worth sitting with. Nearly every piece of synthesizer software, professional or pedagogical, eventually chisels itself toward completeness — save states, polyphony, MIDI mapping, preset browsers — each addition another cut that pushes a living sound device into a category the industry has already fully named and priced: "the synthesizer." That category is itself already-construct, the settled sediment of a finished chisel-construct cycle. What makes beeper different is that it could keep cutting in that direction and chose not to. Sixteen knobs isn't a technical ceiling; it's a decision, and that decision is what keeps the thing wedged in the unwelded gap between toy and tool.

There's a second thing worth noticing: the same logic lives two lives at once, half in an ESP32's registers and interrupts, half in a browser's WebAssembly sandbox, and the whole source sits MIT-licensed on GitHub, open to anyone's fork. That means beeper's structural logic was never locked into one final shape — the next fork could grow it into something else entirely, and even its author hasn't foreclosed what that might be. This is exactly what separates a remainder from a construct: a construct is delivered, named, done changing; a remainder keeps carrying the open question of "not yet judged," and nobody, including its maker, has settled what comes next.

Why does it matter to look at this now, before it gets folded into some retrospective lineage of "minimalist synth toys"? Because once it's named that way, beeper stops being a thing people are still poking at, still forking, still arguing over in comment threads about whether it's actually fun — and becomes a case study, a footnote with its verdict already stamped. The Hackaday writeup is itself the moment when geek culture's own judgment apparatus is slowly closing in on it without having pinned it down yet — the comments underneath are still arguing over whether it's a toy or a teaching tool, and that unresolved argument is the proof the remainder hasn't cooled. To look at it now is to catch judgment before it closes. Any later, and all that's left to see is the instruction manual written after the verdict.

Han Qin (秦汉) · @hqinjarsy · SAE Judgment & Aesthetics