3 ms·
"Creative work destroyed" is scaremongering. All the old versions of Inform are available, so people who have already written games can build and release a new
by skybrian 7y ago
"Creative work destroyed" is scaremongering.
All the old versions of Inform are available, so people who have already written games can build and release a new version of their game just like they always could.
It will be great to see an open source version and maybe this will result in improvements that attract new authors, but in practice, Inform 7 being a closed-source tool has not been any trouble for existing game authors and the risk is no greater than before.
- kragen 7y agoIt is extremely well founded scaremongering. Almost every creative work in a format only accessible via proprietary software becomes unreadable in fifty years or less, an eyeblink in human intellectual history. That risk has always been the same. The few exceptions are things built on proprietary software that was so popular that open-source clones exist — a relevant example in this case being the Z-machine. Creative work built on proprietary software is like a sand castle below the high-tide line, except that the tide won't try to monetize your castle by bundling malware into it.
- skybrian 7y agoA game created in Inform 7 runs on a Z-machine emulator. (Or Glulx, its successor.) This just isn't a problem. Open source emulators are available. You don't need Inform 7 to run old games from ifarchive.org. (Often, authors release their games without source, so having Inform 7 wouldn't do you any good anyway.)
- dwheeler 7y agoThat assumes that the only relevant article in the long term is the executable code. But I don't think that's true at all. The Lyons book on Unix, and several books about the Linux kernel, have shown that the source code also matters. If you can't correctly interpret the source code, the source code is far less useful. So if source code is also important (and it is), then having a publicly-known way to process the source is also important.
- kragen 7y agoThank you for saying this, David. I wanted to say it but I had already lost patience with the discussion. BTW, speaking of the source-code archival problem and also your work on the Karger–Thompson attack, have you been following the work on Mescc?
- dwheeler 7y agoI've been semi-following the bootstrappable builds stuff in general - that work is already listed on my page https://dwheeler.com/trusting-trust https://dwheeler.com/trusting-trust Mescc is obviously an example. Years ago Bellard demonstrated a bootstrap using tcc to compile the Linux kernel (which was pretty amazing). I think the approaches could work together well. Bootstrappable builds reduce the size of the binary you have to trust, and DDC can act as a check on a binary. Thanks for asking!