I wrote a DOOM clone in my own programming language
Raycasting DOOM clone built to stress-test a custom language's C-interop.
A 3D raycasting engine running inside a TrueType font's hinting virtual machine
Raycasting engine in 6.5KB of TrueType hinting bytecode—font VM as GPU.
Programmers interested in constraints, demoscene enthusiasts
The glyph "A" in the font has 16 vertical bar contours. The hinting program reads player coordinates from font variation axes via GETVARIATION, does DDA ray marching against a tile map in the storage area, and repositions bar heights with SCFS. It ends up looking like a crude Wolfenstein-style view.
Small visuzlization: https://github.com/4RH1T3CT0R7/ttf-doom/blob/main/docs/media...
About 6.5 KB of bytecode total - 13 functions, 795 storage slots, sin/cos lookup tables.
JS handles movement, enemies, and shooting, then passes the coordinates to the font through CSS font-variation-settings. The font is basically a weird GPU.
The weirdest parts: - TrueType MUL does (ab)/64, not ab. So 1*4=0. The DIV instruction is equally cursed. - No WHILE loops. Everything compiles to recursive FDEFs. FreeType limits call depth to ~64 frames. - SVTCA[0] is Y, SVTCA[1] is X. Of course.
There's a small compiler behind this - lexer, parser, codegen - that turns a C-like DSL into TT assembly.
Demo GIF: https://github.com/4RH1T3CT0R7/ttf-doom/blob/main/docs/media...
Live demo: https://4rh1t3ct0r7.github.io/ttf-doom/ (Chrome/Edge, WASD+arrows, Space to shoot, Tab for debug overlay)
This is a DOOM-style raycaster, not a port of the original engine - similar to DOOMQL and the Excel DOOM. The wall rendering does happen in the font's hinting VM though. Press Tab in the demo to watch the font variation axes change as you move.
Raycasting DOOM clone built to stress-test a custom language's C-interop.
Convenient Raycast wrapper for a problem npm install -D already solves in two seconds.
Dropped the framework to write raw ANSI codes, slashing startup time from 190ms to 20ms.
It tames Spotlight by scoping searches to user-configured folders and applying exclusion globs (node_modules, site-packages, .git), then re-ranks results by a 60% relevance / 40% recency mix so recent, relevant files bubble up. The pipeline is simple and practical — Raycast → Python → mdfind → filter+rank → JSON — which makes it a quick win for anyone annoyed by noisy Spotlight results, but it’s more pragmatic engineering than breakthrough research.
Yet another font manager when Font Book and iOS already handle this.
Four Claude Code surfaces coordinate to run real Doom with MCP letting the AI play itself.