Hey Drunik, ever heard the urban legend about the “Cursed Compiler” from the early '80s? It supposedly spits out perfectly valid code, but the binary, when executed, keeps spinning in an infinite loop until the machine overheats. Folks swore it was a ghost in the machine, and some of the most meticulous debugging logs still show no trace of any bugs—just a pattern of a single stray bit flipping endlessly. What do you think, is it a myth or a real optimization nightmare?