This is a zero-player-game, a so called "no-player game" or simulation because no human players are actively involved in playing it. Wikipedia

• Tech Stack
• Design
• Features
• Definitions
• How to run
• Approach
• Learnings
• Resources

• Vanilla JavaScript

• Jest (for Testing)
• JSHint (for code quality)

• p5 (for drawing)

Each cell has 8 neighbours, even the ones at the edge of the universe.

1. A dead cell will come alive if exactly 3 neighbours are living.
2. A living cell will stay alive if 2 or 3 neighbours are living.
3. A living cell with less than 2 neighbours will die of underpopulation
4. A living cell with 4 or more neighbours will die of overpopulation.

In short this means:

• 0 -> 3 live neighbours -> 1 (A dead cell will come alive if exactly 3 neighbours are living.)
• 1 -> <2 live neighbours || >3 live neighbours -> 0 (A living cell with less than 2 or more than 3 living neighbours dies.)

• universe: 2D grid
• 2D grid: consists of columns x and rows y

• Use npm test to run the tests
• Use npm run test:watch to enable the Jest watch mode to run all the tests
• WebStorm: If you are using WebStorm as IDE, add --experimental-vm-modules node_modules/jest/bin/jest.js jest --verbose to the 'Node options' of the Jest-Tests run configuration and run them with that.

You see a visual representation of the game running in an endless-loop on this page here. If you want to trigger a fresh initial start of the game, reload the page in the browser.

I am using TDD to evolve the implementation. This means:

1. I first write one or more failing test/s
2. Then I implement the "simplest" possible solution code till the test/s passes
3. I refactor the solution code (till the test/s passes again)

• Using ECMAScript modules in Jest is still experimental!
• Consider the following when running Jest in combination with JavaScript modules.

The --watch option is used to enable Jest's watch mode. When you run Jest with the --watch flag, it sets up a persistent process that watches for changes in your project files.

• In TDD I still struggle with the step: Then I implement the "simplest" possible solution code till the test/s passes. Implementing a first bunch of basic tests can be quite simple and straight forward but as things move on we need to add more logic in a higher dose. Not rushing ahead in that moment is crucial.

• In the sketch.js, we provide our own implementations of the p5js functions that define how the sketch should setup, update, and optionally preload assets. This is not so much overriding (as in object-oriented programming) as it is defining these functions for p5.js to use. Then we need to assign the functions to the global window object to ensure they are properly recognized by the p5.js library.
• p5.min.js: basic library for the processing.
• p5.dom.min.js: this library is specifically focusing on HTML manipulations and interactions. It provides a simple way to interact with HTML5 objects, such as the canvas, video, audio, and more.
• p5.sound.min.js: is an extension library that provides web audio functionality for the p5.js library. The p5.sound library expands upon the Web Audio API and includes features such as audio input, playback, analysis, synthesis, sequencing, scheduling, effects, recording, and more.

• p5.js Reference
• cdnjs
• p5js
• Creating a Local p5.js Project
• Learn p5.js: Fundamentals
• p5.js Tutorial (geeksforgeeks)
• Sound manipulation in p5.js

Made with a 🙂 by Simon Berner