The Baseline Interpreter: A Faster JavaScript Interpreter in Firefox 70

Re:The Baseline Interpreter: A Faster JavaScript Interpreter... by _bxg1 on Friday August 30, 2019 @02:35PM (#20841252)

That's not the same thing; asm.js is a precursor to WASM which is a bytecode language that doesn't include garbage collection, and asm.js is actually an interpreter for it that's written in JS. The JS bytecode the article talks about is generated from JS and interpreted by C++.

In other words, it isn't practical to compile JS to WASM, and especially not to asm.js. The browser's JIT compilation of JS targets something completely different.

[ Parent | on HN ]

Re:The Baseline Interpreter: A Faster JavaScript Interpreter... by XCSme on Saturday August 31, 2019 @07:16AM (#20845655)

I was mostly replying to this: "JS developers don't have the option to send along some of this information themselves; type information, JS bytecode", that in JS you can send some type information with asm.js hints (or TypedArrays), but yes you don't send it directly to the C++ interpreter, but to the JS interpreter, which presumably will pass it further.

[ Parent | on HN ]

Re:The Baseline Interpreter: A Faster JavaScript Interpreter... by erikpukinskis on Friday August 30, 2019 @09:16PM (#20844062)

The point is, if you care about performance use asm.js. If you don’t then just use whatever standard path browsers provide and any optimization they do is gravy.

[ Parent | on HN ]