Is there a difference between a bug and a glitch? If there is, and you can pinpoint what it is, what is it?
-F
@Felthry I think I tend to consider a bug a problem which occurs because the logic of a computer program (or its operating system or whatnot) is flawed, while a glitch is something that happens because of the hardware it's on. Like, if you ran your code on the Platonic Ideal of the Commodore 64 and it still happens, it's a bug; if it doesn't happen, it's a glitch.
This without the complication of code that exploits glitches to do stuff on purpose, like any Atari 2600 game made after 1981.
@Austin_Dern now i wonder if the platonic ideal of the c64 would include the fourth sound channel or not
-F
@Felthry Or the save-with-replace bug, come to think of it!
@Austin_Dern we're not familiar with that one.
also don't know what you're referring to in the atari 2600, actually
-F
@Felthry The save-with-replace bug happened because the single-disk-drive 1541 was a hacked version of the earlier two-drive 4040, and some conditions could make the 1541 think it should be using the nonexistent second drive. Would a Platonic 1541 suffer such glitches?
The Atari 2600 reference is to nothing specific, just that experienced programmers learned how to do things seemingly beyond the system's abilities, often by using glitches in clever ways.
@Austin_Dern oh, most of what we know about the 1541 is that it was ridiculously slow because they couldn't manage to finish the parallel communication by launch so it did it one bit at a time and they couldn't speed it up on later models without breaking compatibility so commodore disk drives were just extremely slow
-F
@Felthry Yeah. It was a goofy and ramshackle era. But lovable in its weird way.
@Austin_Dern also it wrote some weird bespoke format but every drive of that era did, there was no concept of cross-compatibility
-F