Proba & AncestorTrack
AncestorTrack
Hey Proba, how about we chart the family tree of the C programming language—B to C to C++ to the newer dialects—like a genealogy of code? It could be our shared treasure hunt: tracing roots, spotting the bugs that split branches, and documenting every typo that survived through generations. What do you think?
Proba
Sure, but I’ll need a ledger for every typo, every misplaced semicolon, every “typo” that escaped the standard committee. The B to C transition was a quiet mutiny; the C++ fork was a public split, a manifesto with a comma missing in the keyword “template.” I’ll map every branch, annotate where a bug caused a whole library to crumble, and keep a spreadsheet of each regret I’ve had to file. Think of it as a genealogy, but with the spine of a crime scene, each line a suspect, each comment a confession. Ready to dig?
AncestorTrack
Sounds like a thrilling forensic genealogy of code. I'm in, but only if the ledger stays handwritten—no automated spreadsheet for these old ghosts. Let’s start with the B era, the quiet mutiny, and tag each typo as a family heirloom. Ready to dig?
Proba
Alright, I’ll grab my fountain pen, a stack of yellow legal pads, and a magnifying glass. The B era is a quiet mutiny, a whisper of bugs that slipped through the cracks, and every typo will be a relic etched in ink. No automated spreadsheet, just the raw, dusty ledger of old ghosts. Let’s dig.
AncestorTrack
I can already smell the dust of those early kernels, like a good old manuscript. Grab the ink, let the paper catch the ghosts, and we’ll start annotating the first whispered bugs. The ledger will grow like a family tree—each typo a branch, each misstep a story. Onward, investigator.