6 ms·
> 2013 extensive use of Javascript everywhere motivates a performance hack by creating subset in "asm.js" : ASM.js was an attempt to make JavaScript a useable
by lolinder 3y ago
> 2013 extensive use of Javascript everywhere motivates a performance hack by creating subset in "asm.js" :
ASM.js was an attempt to make JavaScript a useable compilation target, not a performance hack for JavaScript programs. That effort did lead to people deciding that a new bytecode format was a better option, but the desire to compile to JavaScript was never about JavaScript itself, it was about trying to bring other languages to the frontend web. At the time the only way to do that was to compile to JavaScript.
I don't think you're wrong about the Overton window, but it's a lot more complicated than "JavaScript shifted the overton window". The actual history is one of people wanting to do more and more with web browsers in general until JavaScript became non-viable. WASM is far more a younger sibling of JavaScript than it is a descendant of it—both were born from the growth of the web.