I would agree this is ugly, and would probably be more clear if written more verbosely. I'm *guessing* this is to ensure we have an intervening frame change before running the next step, because a lot of our code gets scheduled with requestAnimationFrame