An updated version of the classic "Basic Computer Games" book, with well-written examples in a variety of common MEMORY SAFE, SCRIPTING programming languages. See https://coding-horror.github.io/basic-computer-games/
Buzzword: I declared separate arrays for the data, instead of a single 39-member array; and I set it to check for "n" instead of "y" on if to keep going, or not.
RockScissorsPaper: made use of an enum to spell out how you or the CPU won, vs a blanket statement. Had some help from the Nim Discord on how best to use the enum.
The Nim Discord folks had a more-optimized version of the RSP outcome function; included that in a follow-up commit; you can compare them to see how one works vs the other.
Took some liberties with both of these...