I think a lot of platforms today could be transformed if they had someone doing a similar contribution to Fred Fish.
I wouldn't be capable of such an effort, I think few people are, and I'm not sure if it can be done in any monetized way. The motivation has to be purely for the quality of the job.
I still gotta play the quirky text adventure game called Fish..
Not obscure games
(and no, that game is not on this site)
Epic to see that it has "No Man's Land" [0] and really really weird feeling to read the readme. No idea why it's listed as a "17 Bit" title though, perhaps they distributed it at some point but they certainly were not involved in creating it. Source: I wrote it. Fun times.
Edit: formatting.
But Amiga has a 16 bit CPU... or not?
BTW, I don't think the software in this repository is compatible with PPC-based Amigas, is it? (Unless they have the add-on board that runs a 68000-series processor in parallel?)
And it would still run 68K code on "companion" 040/060
http://www.phase-5-digital-products.com/TheLegacy/amiga/b603...
(So to everything around the CPU they were 16-bit even though internally they could do 32-bit computations)
Also worth nothing that it's just the early 68Ks that came with a narrow external data bus. The 68020 and onward, which were also used in the Amigas, have a 32 bits wide data bus.
My favorite so far is the "Iff Specs Disk", with technical documentation on an ancient container and data format called IFF (Interchange File Format).
Like in the file ea.iff.85 [0], and this section explaining why common data file formats are useful the first place:
"The problem with expedient file formats - typically memory dumps - is that they're too provincial.
By designing data for one particular use (e.g. a screen snapshot), they preclude future expansion (would you like a full page picture? a multi-page document?).
In neglecting the possibility that other programs might read their data, they fail to save contextual information (how many bit planes? what resolution?). Ignoring that other programs might create such files, they're intolerant of extra data (texture palette for a picture editor), missing data (no color map), or minor variations (smaller image).
In practice, a filed representation should rarely mirror an in-memory representation. The former should be designed for longevity; the latter to optimize the manipulations of a particular program. The same filed data will be read into different memory formats by different programs."
Imagine having to explain to a professional developer today why having something like JSON is valuable. Most of us find it obvious.
But there was a time when this kind of thing was not obvious at all; the need for it had to be discovered the hard way, and then solutions invented from first principles.
We really are standing on the shoulders of those who came before us, in more ways than we realize.
[0] https://amigafreeware.downer.tech/17bit/17bit/61/contents/if...