Compare game runtimes with a shared prototype

A shared prototype makes discussion across runtimes concrete. Implement the same movement rule, asset and restart behavior before comparing language syntax or framework convenience.

Record the assumptions each runtime handles for you: scene lifecycle, audio, input and resizing. Then record the code you must write yourself. This reveals a practical tradeoff more clearly than a list of features.

Keep the core rules platform-neutral where possible. A deterministic board or movement test can validate behavior while the input and drawing layers change. Use the tutorials below to build that comparison.