> In the most performance-sensitive contexts, JavaScript hinders rather than helps. Its dynamic type system and non-deterministic garbage collection pauses get in the way. Seemingly small code changes can result in drastic performance regressions if you accidentally wander off the JIT’s happy path.
I'm seeing this repeated more and more as a compelling case for using WASM. I've even repeated it myself. Does anyone know of examples of JS optimized for one VM not performing well in others, leading to a significant cost? I ask this as a Rust/WASM fanboy. Not doubting; just curious. I feel like I've already read a couple anecdotes but can't remember.