Profiling. So much profiling. Of course for that to be relevant you need to have tests that can actually hit the relevant code paths. The fastest(hah!) way to

Profiling. So much profiling. Of course for that to be relevant you need to have tests that can actually hit the relevant code paths. The fastest(hah!) way to get performance of something fixed is to provide a easy to run deterministic and vaguely realistic example where performance is significantly worse in one case vs another. Now that could be one JS engine vs another, but it could also be a piece of JS calling two functions doing the same thing, only one in JS and one in wasm, or say a switch vs a series of if/else