> The demo is run on an x86 emulator that records every block of code the CPU actually executes, over the whole demo.

> That recording is translated into C - the original instructions, one for one, with the exact cycle timing of the emulated machine.

What's the advantage of this approach vs cycle-accurate emulation? (I'd guess it can go faster, due to compiler optimization?)

> The result is checked against the emulator event for event: every interrupt, port access and frame at the same moment of emulated time.

It's funny how LLMs leak their test procedure docs into user-facing output.

So much fun. I recently ported some old strategy games. Claude does it almost on its own http://replicated.live/blog/games

This kind of made me sad.

The demoscene was all about human ingenuity getting the most out of the machine. It was about showing off how good your crew was at making things from nothing but their minds.

Now, it too, has been swallowed by the AI that is destroying this entire mode of being, the joy and creativity of writing code, of solving seemingly-impossible puzzles with ones mind.

My favorite creative and intellectual outlet is dying off and its killer is wearing its corpse as a costume.