A Compiler Writing Journey

A GitHub diary charts one developer’s epic quest to build a self-compiling C compiler—yes, a program that can compile itself—step by step, from scanning text to spitting out assembly, even flirting with retro hardware. Then, plot twist: he pauses the project and starts a new language called alic. The build log reads like a training montage, and the comments? Like a boxing ring.

The loudest rumble: language choice. One commenter sighed, “I can’t imagine writing everything in C,” while learning OCaml (a language beloved for compiler projects). That stirred a mini flame war: C loyalists flexed their “real metal” cred, while OCaml fans swore by fewer footguns and more sanity. It’s grit vs comfort, with plenty of popcorn. For the uninitiated, a compiler is the tool that turns human code into machine instructions; OCaml is a functional language many use to write them.

Then came the cheeky bomb: “How much of Claude was used?”—a wink at the AI assistant. Cue memes about “self-compiling vs self-composing,” plus side-eye about AI credit. There’s no evidence AI touched the project; it’s just the internet being the internet. Bonus chatter gave props for clear licensing and credit to SubC, because open-source nitpicking never sleeps. The takeaway: one person’s hardcore build log became a community soap opera.