> (ie-Browser makers put in spectre and meltdown mitigations, and changes in WASM allow WASM content to get around those mitigations.) Could you be more specif

> (ie-Browser makers put in spectre and meltdown mitigations, and changes in WASM allow WASM content to get around those mitigations.) Could you be more specific? I implemented Chrome's Spectre mitigations for WASM and I'm not sure what you are referring to. > Should probably mention that the upcoming changes include threading and shared memory. These only give you a high-resolution timer mechanism--which you have to build yourself and is possible in JS with SharedArrayBuffer before. So WASM is no worse in this respect.