#0001
Firefox 148 Starts Turning Off `asm.js` Optimization
40radar
Legacy asm.js still runs, but loses its fast path in Firefox. Old web games and compute-heavy demos should move to WebAssembly; new products can ignore this.
- From
Firefox 148, SpiderMonkey disablesasm.jsoptimization by default, with removal planned later. - Compatibility remains because
asm.jsis a JavaScript subset; the breakage risk is performance, not execution. - Existing
asm.jsassets should be migrated toWebAssembly. For new builds, do not target asm.js.
Source: news.hada.io/topic?id=29732Read original →