> Where in the article does it say "the code in question ... is displayed on screen"? As someone else mentioned, it shows up in the GIF animation, about 45 se

> Where in the article does it say "the code in question ... is displayed on screen"? As someone else mentioned, it shows up in the GIF animation, about 45 seconds in, as a sequence of text boxes. https://i.stack.imgur.com/8Aznd.gif https://i.stack.imgur.com/8Aznd.gif > Your assertion about "reliable way of making basic sounds" is sort of true, if you ignore the shonky hardware that used to and get shipped as a "speaker". On the IBM PC, one of the channels on the PIT (programmable interval timer) was hooked up to a speaker. It didn't sound great, but it could at least make simple tones on its own, and even music, without sucking up too much CPU time: https://www.youtube.com/watch?v=1IOL4q5tDDQ https://www.youtube.com/watch?v=1IOL4q5tDDQ The Apple II had it much worse. It had a built-in speaker as well, but no timers -- the speaker was connected directly to the memory address $C030, such that performing a read or write operation on that address would toggle the state of the speaker (on/off). Playing a tone required the CPU to hit that address in an appropriately sized loop; since the CPU wasn't particularly fast to begin with, it was nearly impossible to play audio while anything else was going on.