Introducing Bundle Compiler

Re:Introducing Bundle Compiler by nathancahill on Tuesday August 29, 2017 @01:56PM (#15126204)

> Once we have loaded the program we simply set the program counter to the handle and start executing the VM.

Seems like a perfect use case for WebAssembly once it's adopted. Instead of each framework creating their own bytecode implementation and VM to match it.

[ Parent | on HN ]

Re:Introducing Bundle Compiler by zzalpha on Tuesday August 29, 2017 @01:57PM (#15126228)

I'm baffled... why aren't they compiling to JS? They're cheating the runtime out of the ability to JIT the resulting code, which seems like a huge penalty.

[ Parent | on HN ]

Re:Introducing Bundle Compiler by yorwba on Tuesday August 29, 2017 @03:32PM (#15126966)

I'm assuming that most of the runtime cost is in the actual DOM manipulation, so unless the JIT can inline and optimize those calls, doubly-interpreted code isn't going to slow down things much.

However, what they seem to be going for is a reduction of the time it takes to download and parse the code, so a specialized compressor makes sense. WebAssembly or the Binary AST proposal would change the calculation, but maybe it still works for them.

[ Parent | on HN ]