Yes, stimulating sounds weird. But simulating sounds boring. So I wrote FlowSnakes to show how pre-emptive multi-tasking really works—not at the microsecond level, but at the 1/64th second level—closer to the keyboard than to the chip:
The snake class has DNA for four kinds of snakes. Flowser and Flowsie are like brother and sister—one blue, one green, same speed, same length. Nemesis is longer and faster—he's out to get Flowser and Flowsie. Bruiser is short and slow—but he can almost walk thru walls.
Each snake has his/her own QWERTY controls:
The FlowSnake game is in a deliberately undercoded state, and I don't mean Ohio. Just one example, snakes bounce back rather than turn when they hit a wall. Existing FlowSnake code is part of a larger curriculum initiative at www.praxismachinecodinglessons.com/async-excel-snakes.htm
When better snakes are built, better high school students will build them, but I digress.
Meantime, you are welcome to practice your multi-snake dexterity, review snake class code and initialization routines, propose improved snake behaviors, and critique the pedagogical thrust of FlowSnakes in general.
Also, please let me know if you can break the existing snakes in new and interesting ways.