51 slowly but surely getting rid of all the tuples that I used in arena_keeper.
another thing that used to worry me was the size of the .wasm file that I was dealing with (4.1 MiB), however as it turns out the default of cargo web deploy is debug mode and giving the flag --release with it causes it to spit out a 897.4 KiB file instead which looks a lot more manageable. Especially considering a site I worked on at work spits out a 793.87 KiB js file AND a 896.07 KiB js file.
And not only is my current file a good bit smaller than both of those together, .wasm files also don't spend nearly as much time being read as js files so my time until execution should be quicker even if they where the same size. In fact, .wasm files can even be parsed while its still being downloaded which isn't the case for JS files which increases this advantage even more.
And, if that is still not enough I should have some extra tricks up my sleeve, like changing the default malloc implementation that is used, and throwing the compiled .wasm file into wasm-opt which should try to make it even smaller.
So... I think I should be good on that front as well? At least for a little while
