I’m not the person who wrote the original comment, but again go back to my example of Space Invaders, if it had been archived that way it would now be essentially lost, because running a copy that was archived that way would cause the issue I described on my other comment. So I don’t understand your point, this is objectively worse in terms of preserving games, it might cause unwanted behavior that you’re not predicting, an emulator is not perfect, but can compensate for these things by emulating the hardware.
it’s not a valid comparison really. this is an alternative to an emulator than a ROM.
If you used this to compile a native version of space invaders that ran incorrectly it would be no worse than if you used an emulator to run space invaders that ran incorrectly. in either case you treat it as a bug in the emulator/recompiler and fix it and re run the process.
Nobody is suggesting deleting their roms and keeping only the current copy of a recompiled game. I don’t think that would even work… as far as I know you still need the original ROM to load inside of the recompiled executable for the non-code assets.
First of all this is a chain of replies to someone who said that this would be the way to maintain games for the future. So that’s the argument that’s being attacked here.
Secondly with an emulator you can emulate hardware, so recompiling space invaders would cause the issue I mentioned and you wouldn’t be able to fix it because it’s a “bug” in the original code (not really a bug, but rather using hardware limitation as a feature), and my point is that you don’t know what sort of similar issues you might find here, therefore this is the worst format for preserving old media, ROMs and emulators are better for preserving (which again is the discussion here)
While I agree that ROM + emulator is best for preservation, you absolutely can fix the space invader bug because you have the C code which would let you add in delays. Just like there are many versions of Space Invaders for different consoles an none of them use emulation but play like the original. I’m a fan of si78c, a memory accurate reimplementation of the 1978 arcade game written in C.
Of course Space Invaders wasn’t written in C so this new tool doesn’t apply.
But the article does talk about how the decompiler sometimes introduces bugs and how they were manually fixed before compiling.
So you were right but the problem you brought up has already been addressed. (And will continue to need to be addressed as more cross compiling bugs are found in each game.)
I interpreted the word “legacy” the OP used as the fandom for old games rather than perfect preservation.
Ah, i think i misunderstood your comment.
In terms of archiving I agree, in terms of restoring a running copy from an archive, maybe not.
I’m not the person who wrote the original comment, but again go back to my example of Space Invaders, if it had been archived that way it would now be essentially lost, because running a copy that was archived that way would cause the issue I described on my other comment. So I don’t understand your point, this is objectively worse in terms of preserving games, it might cause unwanted behavior that you’re not predicting, an emulator is not perfect, but can compensate for these things by emulating the hardware.
it’s not a valid comparison really. this is an alternative to an emulator than a ROM.
If you used this to compile a native version of space invaders that ran incorrectly it would be no worse than if you used an emulator to run space invaders that ran incorrectly. in either case you treat it as a bug in the emulator/recompiler and fix it and re run the process.
Nobody is suggesting deleting their roms and keeping only the current copy of a recompiled game. I don’t think that would even work… as far as I know you still need the original ROM to load inside of the recompiled executable for the non-code assets.
First of all this is a chain of replies to someone who said that this would be the way to maintain games for the future. So that’s the argument that’s being attacked here.
Secondly with an emulator you can emulate hardware, so recompiling space invaders would cause the issue I mentioned and you wouldn’t be able to fix it because it’s a “bug” in the original code (not really a bug, but rather using hardware limitation as a feature), and my point is that you don’t know what sort of similar issues you might find here, therefore this is the worst format for preserving old media, ROMs and emulators are better for preserving (which again is the discussion here)
While I agree that ROM + emulator is best for preservation, you absolutely can fix the space invader bug because you have the C code which would let you add in delays. Just like there are many versions of Space Invaders for different consoles an none of them use emulation but play like the original. I’m a fan of si78c, a memory accurate reimplementation of the 1978 arcade game written in C.
Of course Space Invaders wasn’t written in C so this new tool doesn’t apply.
But the article does talk about how the decompiler sometimes introduces bugs and how they were manually fixed before compiling.
So you were right but the problem you brought up has already been addressed. (And will continue to need to be addressed as more cross compiling bugs are found in each game.)
I interpreted the word “legacy” the OP used as the fandom for old games rather than perfect preservation.