Performance

[deciduously]

On my desktop I noticed no issues, but this thing slowed to a crawl in Chrome on my 2012 laptop. Firefox had no problem.

Stop one is to remove all calls to Game outside of tick() and pack() and restart(). Things like "last_update" and "progress string" (whcih s just num_dots - captured dots, so just pass through the cpatured count and let JS subtract) and "num_dots" should get packed into the Vec - design a series of f32s that hold all the necessary info and put them in front, and then in drawGame handle those values before starting your for loop at the proper offset

[deciduously]

I've now done that - the renderLoop only calls out to game.pack() and game .tick(), everything is included in the packed array.

Still very slow on the older laptop in Chrome, and perfectly fine in Firefox.

[deciduously]

separating the header u8s from the dots u32 didnt help...