Conway's Game of Life in Google Docs
Conway's Game of Life in Google Docs
Swizec Teller decides to build Conway's Game of Life in Google Docs, just for fun.
Join the DZone community and get the full member experience.Join For Free
Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.
Have you really never wanted to create Conway’s game of life in a Google Doc spreadsheet? Really, never? Okay, it’s a pretty weird thing to do. And it’s not as fun as I hoped.
You can play with it, here.
That’s easier, but still… how? You can’t just show them a bunch of for loops and functions and hope it sticks. You have to get them excited.
The question I’m trying to answer is: “How can this make my life better?”
They all spend a lot of time in Google Docs. They run a lot of day to day processes in there. Google Docs has scripting capabilities.
See what I’m getting at?
Conway’s Game of Life inside Google Docs, of course. It highlights the basics of reading and manipulating properties of individual cells in spreadsheets, and the game itself is easy to explain:
- Any live cell with fewer than two live neighbours dies, as if caused by under-population.
- Any live cell with two or three live neighbours lives on to the next generation.
- Any live cell with more than three live neighbours dies, as if by overpopulation.
- Any dead cell with exactly three live neighbours becomes a live cell, as if by reproduction.
I showed one of them some GIFs and he said “Oh dude, I’m excited! That looks so cool.” All the confirmation I needed to go waste 3 hours of my life figuring out how to build this!
Scripting Google Docs is hell.
You can’t alert, there’s no console.log, everything is slow, and ES6 works only partially. You get destructuring, but no string templates. I dared not try arrow functions.
Timers also don’t exist. Which means you have to manually step through the game loop by clicking a button.
One silver lining is this 3rd party logger called BetterLogger, which lets you
Logger.log things to a separate sheet in your spreadsheet. It’s not very smart, but it helps a lot.
And if you thought DOM was slow, wait til you try Docs access. Naively searching through 30×30 cells and counting neighbors took many seconds. Maybe 20 seconds per game tick.
That can be optimized, though. Just access the spreadsheet less.
The first step is to set global vars and add a menu:
Docs runs this code when you open your document. It adds a menu that looks like this:
Step Game runs an iteration of the game loop,
Clear Game clears all cells. Black background means a living cell and white background means a not-living cell.
On each game step, we build a map of living cells, then run the game rules on each. Like this:
You can think of the spreadsheet as 2-dimensional memory. First dimension is the row, second is the column. You can store styling information, the value itself, and notes. Docs lets you access directly on both dimension, but it’s slow.
Having 2D memory also means there will be a lot of these nested for loop constructs in your code. You’re limited to O(n2) algorithms at best.
Applying Conway rules to each cell looks like this:
We count living neighbors, discount the current cell if it’s alive, then decide whether to
activate it. Counting the neighbors literally means walking through a 3×3 array around the current cell and counting cells that have a black background.
Activating or deactivating is a call to
That’s kind of it… I’m embarrassed it took me 3 hours...
Published at DZone with permission of Swizec Teller , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.