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
@Austin_Dern come to think of it, the distinction between hardware and software is a bit blurred with cartridge games
people would think of the cartridge for, say, star fox as being a medium for holding the software because that's what rom cartridges were originally meant for
but the star fox cartridge also contains the superFX coprocessor, without which it won't work
-F
@Felthry Yeah, this is another aspect of cartridge games that makes it impossible to make a perfect and unambiguous divide between bug and glitch.