Austin Shijo, a statistics student at IIT Kanpur (GitHub: mTvare6, X: @epestr_0), was reading a CMake tutorial when he ran into a line dropped almost in passing — that a ray tracer could theoretically be written in any language. He decided to test that claim against the simplest language he knew: Brainfuck, an esoteric language with exactly eight symbols — pointer movement, cell increment and decrement, input and output, loop brackets — plus a single, unbounded tape of memory cells. No variables, no functions, no floating point. Rather than hand-typing the thing, he built a compilation pipeline: the C code for the "Metal" chapter of Peter Shirley's Ray Tracing in One Weekend, a scene nearly every graphics beginner has rendered at some point, gets converted to static-single-assignment form, compiled into a custom intermediate DSL of his own design, and only then lowered into Brainfuck. To handle the oversized sphere standing in for the ground, he swapped the usual Q8.8 fixed-point format for Q16.16, and rebuilt from scratch everything a graphics library normally hands you for free: multiplication by repeated addition, division by long division with remainder tracking, square root via a long-division integer isqrt, a mod-256 linear congruential generator for randomness.

On content alone this is nothing new. Ray tracing has been taught to exhaustion by Shirley's book; Brainfuck has been an esolang-community plaything for three decades, named and re-named many times over. SAE's judgment of a remainder never rests on whether the content is novel — only on whether the logic is still growing. What hasn't been settled here isn't the algorithm or the language, but the thing sitting between them: how to correctly compile arbitrary numeric computation onto an eight-symbol tape. Shijo's pipeline — C to SSA to DSL to Brainfuck — is scaffolding he built on the spot, and nothing about it has been shown to be optimal, or even correct in any generally agreed sense. The compiled scene came out to 23 megabytes of Brainfuck, heavier than the 0.9-megabyte image it renders. That inversion is itself physical evidence of the remainder: the part of the chisel-construct cycle still alive — the design of the compiler, the shape of the abstractions — outweighs, in literal bytes, the finished thing it produced.

The post went up on September 24; two days later it reached Hacker News and picked up eighty-eight points, and pushback arrived fast, in two registers. The milder objection questioned the framing itself — this isn't writing a ray tracer in Brainfuck, it's writing a C-to-Brainfuck compiler — which Shijo conceded outright, saying the interesting part was never the 23 megabytes of raw output but the compiler and the abstractions that generated it. The sharper objection came from Daniel Cristofani, a Brainfuck programmer whose name carries real authority in that small community: he pointed out that Shijo's position-agnostic encoding collapses the tape's Turing-complete expressiveness down to something closer to a finite automaton, that excessive copying and zeroing bloats the generated code, and that the tape is left littered with uncleared garbage — a technically informed bad review from someone who actually knows this language's inner texture. Shijo's reply wasn't defensive; he called the project exploratory rather than optimal, and said he'd go study the proper technique. That exchange is itself proof that nothing here has hardened into construct yet: there isn't even a settled answer, among the people who actually know this language, for what correctly compiling numeric code to a Brainfuck tape should look like.

That's exactly why the moment matters. Once critiques like Cristofani's get absorbed and some canonical way of compiling to a tape machine gets written into a tutorial or a library, this scaffolding stops being remainder and becomes construct — the next person will just reach for the known technique, and no one will be teaching it live in a comment thread. Right now it's still a half-flawed specimen a statistics student built on a whim, getting corrected in real time by someone who actually knows the terrain — which is precisely the window the beauty of the remainder exists to catch.

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