"This masking strategy would in turn require a power-of-two related memory size, and there has been a lot of resistance to this too."
And try to think about the implications it has on the memory model of the VM that is going to execute/JIT Webassemly.
A power of two memory model, isn't really viable at this level I think. And you don't need to think a lot about it, to figure out that jumping to 256MB memory, just because your app/page needs 130MB is a bit of counter-optimization :)
The resistance is the sensible thing to do in this case :)
"This masking strategy would in turn require a power-of-two related memory size, and there has been a lot of resistance to this too."
And try to think about the implications it has on the memory model of the VM that is going to execute/JIT Webassemly. A power of two memory model, isn't really viable at this level I think. And you don't need to think a lot about it, to figure out that jumping to 256MB memory, just because your app/page needs 130MB is a bit of counter-optimization :)
The resistance is the sensible thing to do in this case :)