GAME.removeChild(rock) VS rock.remove()

[ecssiah]

It might be worth offering a slight hint to remove the rocks by using their remove() method rather than using the removeChild method on the GAME element.

Using removeChild led to a REALLY confusing bug that caused me to spend 99% of my time getting the endGame() test to pass ; )

I'm thinking that's because the remove() method gets rid of all the bound events to the element, and removeChild does not. There is still a number of suggestions around the internet to avoid remove(), because it isn't well supported.